FAQ

Foundational Questions:

Q: What is 4QX in one sentence?

A: 4QX is a formally verified framework where two cybernetic loops (Class and Instance) share a single public seam, executing a six-phase cycle that provably converges to maximal availability (H=0).

Class and Instance triangles sharing the public seam; no Resource–Metric shortcut (HOL-VIS-002)
Two lifecycles — Class and Instance — share the public seam only.

ListenTwo Triangles, One Seam · Diagrams

Two Triangles, One Seam
Q: Why “4QX”?

A: The “4Q” refers to the four quadrants (TL, TR, BL, BR) formed by two orthogonal polarities (Outer/Inner × Form/Flux). The “X” represents the diagonal feedback loops that transform static categories into an active cybernetic engine.

The four-quadrant field: public Pattern and Event above; private Resource and Metric below; Form on the left, Flux on the right.
Q: Is this philosophy or mathematics?

A: Both, but carefully separated. The mathematical kernel (finite ZF, Lyapunov convergence, idempotence) is machine-checked in Lean 4 with zero sorry. Philosophy enters only as constraints on formal objects, not as implicit axioms.

ListenHow Empty Sets Force a Dual Engine · Diagrams

How Empty Sets Force a Dual Engine
Q: What makes 4QX different from other frameworks?

A:

  1. Machine-checked proofs of convergence and idempotence
  2. Single seam constraint (no BL↔BR) that emerges from geometry
  3. Scale independence from the same mathematical structure
  4. Consciousness-first architecture with self-reference built in
  5. Characterisation theorem: Geometry forces a unique HF ZF fragment (geom_frag_unique_exact)
  6. Universal embedding: 4QX wraps any finite singleton-chain system (proven)
  7. MetaMonism: Void↔everything cycle is scale-independent (proven)
  8. AGI convergence theorem: constitutional_converges proves any Constitutional system reaches H = 0 (the legacy flagBundle_holon_and_encodeHarmony_drain was deleted in Sprint 39.5B — it was hollow). GapMap.lean is at ZERO sorry, all gaps closed.

Architecture Questions:

Q: What are the four quadrants?

A: Two axes — perspective (public/outer vs private/inner) and modality (form/structure vs flux/continuity) — define four roles on one field. Each quadrant is labelled on the diagram:

Each quadrant carries a distinct role: reusable structure, seam-visible activity, private capacity, and execution evidence.
Q: Why can’t BL connect directly to BR?

A: The missing BL↔BR edge is foundational, not arbitrary:

  1. It defines the outer/inner distinction structurally
  2. It forces all effects through the auditable seam
  3. It enables idempotent composition
  4. It preserves sovereignty of private domains
Public seam between Pattern and Event, with no BL to BR private shortcut (HOL-VIS-002)
Public work crosses only the Pattern–Event seam (TL–TR). Resource and Metric are private and do not connect directly.

ListenWhat systems actually promise · Diagrams

What systems actually promise
Q: What is “the seam”?

A: The TL↔TR interface—the single public channel where all cross-holon interaction occurs. It’s where Form meets Flux, where structure encounters the present, and where value is exchanged.

Public seam between Pattern and Event, with no BL to BR private shortcut (HOL-VIS-002)
Public work crosses only the Pattern–Event seam (TL–TR). Resource and Metric are private and do not connect directly.
Reference table: Offer and Accept as one seam event from two sides (HOL-VIS-002)
Offer (Instance) and Accept (Class) are one seam event — commitment visible before private burn.
Q: Why are there exactly two triangles?

A: Given four corners, five edges (no BL↔BR), and the requirement for closed feedback loops that cover all edges, exactly two triangles emerge as the unique minimal tiling. This is proven, not designed.

Class and Instance triangles sharing the public seam; no Resource–Metric shortcut (HOL-VIS-002)
Two lifecycles — Class and Instance — share the public seam only.
Instance loop with numbered GO labels Fit, Offer, Integrate on edges (HOL-VIS-002)
Instance phases on edges: 1·Fit, 2·Offer, 6·Integrate.
Class loop with numbered GO labels Accept, Run, Publish on edges (HOL-VIS-002)
Class phases on edges: 3·Accept, 4·Run, 5·Publish.
Q: How are the feedback signs (positive/negative) determined?

A: Feedback signs are derived from closure-phase geometry (Epic 44), not assigned as role-indexed constants. Both closure phases (CFinish, IFinish) traverse Flux→Form on the horizontal axis — this shared direction is the eligibility gate. They differ only on the vertical axis: IFinish goes World→Self (negative/stabilising), CFinish goes Self→World (positive/amplifying). The truth-lock role_feedbackType_eq_derived proves the existing Role.feedbackType equals this geometry-derived version. The flagship theorem feedbackType_dual proves r.dual.feedbackType = (r.feedbackType).neg. See Philosophy/TelosSemantics/FeedbackWeld.lean and InvolutionLaws.lean.

Q: What is the TelosLeg classification?

A: Epic 44 classifies the six phases into three semantic legs based on their operational character: Walk (active traversal: Pow/Union — IStart, CDo), Seam (mediated contact: Sep/Pair — IDo, CStart), Merge (idempotent fold-back: Empty/Repl — CFinish, IFinish). Closure polarity exists if and only if the phase is Merge (polarity_iff_merge). FieldGO harvest permission is granted if and only if Merge (harvest_iff_merge). TelosLeg is a semantic overlay orthogonal to the geometric Leg; σ swaps Walk↔Merge while preserving Seam. See Philosophy/TelosSemantics/FormFluxPolarity.lean and TelosLegWeld.lean.


Dynamics Questions:

Q: What is the harmony function H?

A: H(p) = debt_coh(p) + debt_flux(p)—a Lyapunov-style potential measuring total system tension. debt_coh is structural tension; debt_flux is processing backlog.

Harmony debt columns with H equals debt_coh plus debt_flux ledger panel (HOL-VIS-002)
H = debt_coh + debt_flux — when both are zero, the system is maximally available.
Reference table: debt_coh and debt_flux component definitions (HOL-VIS-002)
debt_coh tracks pattern–resource shortfall; debt_flux tracks event–metric shortfall.

ListenWhen tension actually clears · Diagrams

When tension actually clears
Q: Why does H always decrease?

A: Each effective step is constructed to reduce one of the debt components. This is proven in the formal kernel—H(step(p)) < H(p) when H(p) > 0.

Integrate and Publish as debt-reducing return edges with gap table (HOL-VIS-002)
Integrate closes the flux gap (TR→BL); Publish closes the coherence gap (BR→TL).
Reference table: flux and coherence gap rows with return phases (HOL-VIS-002)
Which gap each return edge closes — pair with beat 10 when prose walks through clearing.
Q: What happens at H=0?

A: The system achieves maximal availability:

  • step(p) = p (idempotent)
  • No structural conflicts remain
  • No processing backlog exists
  • Both loops become no-ops
Harmony debt columns with H equals debt_coh plus debt_flux ledger panel (HOL-VIS-002)
H = debt_coh + debt_flux — when both are zero, the system is maximally available.
Reference table: harmony ledger formula H equals coherence debt plus flux debt (HOL-VIS-002)
Harmony means H reaches zero within an honestly accounted boundary.
Q: What is a “semantic unit step”?

A: One effective move of the harmony reducer—a single semantic operation that may involve many physical micro-steps but constitutes one unit of H reduction. The seam’s idempotent/commutative properties make this well-defined regardless of implementation details.


The Six Phases:

Q: Why exactly six phases?

A: The six phases map to the six finite ZF constructors (Pow, Sep, Pair, Union, Empty, Repl) in a principled way. The 2-2-1-1 grouping (two Instance openings, two Class openings, two closes) is the unique valid linearisation of the geometric constraints.

Clockwise numbered operator cycle starting at 1 Fit: Fit, Offer, Accept, Run, Publish, Integrate (HOL-VIS-003)
Generic Organisation cycle for operators — clockwise from Fit.

ListenWhy busy workflows never settle · Diagrams

Why busy workflows never settle
Q: What does each phase do?

A:

  1. IStart (Pow): Generate option space from self
  2. IDo (Sep): Filter and expose public offer
  3. CStart (Pair): Bind pattern to specific offer
  4. CDo (Union): Execute privately (the only “burn”)
  5. CFinish (Empty): Publish results, clear obligation
  6. IFinish (Repl): Integrate results into self
Dual triangles with all six numbered GO phase labels and no BL to BR callout (HOL-VIS-002)
Full operator cycle on the dual field: Fit → Offer → Accept → Run → Publish → Integrate.
Reference table: six formal kernel phases numbered 1–6 (HOL-VIS-002)
Kernel names (Pow, Sep, Pair, Union, Empty, Repl) map 1:1 to the Generic Organisation cycle.
Q: Why this specific order?

A: Causal necessity:

  • Must offer before accept
  • Must accept before execute
  • Must execute before publish
  • Must publish before integrate

Conceptual Questions:

Q: What is “dialectical monism”?

A: The stance that reality is One (monism) expressing as Two complementary forces (Form and Flux). These aren’t opposing substances but functional roles within a single unified process.

ListenThe metabolic cost of tracking everything · Diagrams

The metabolic cost of tracking everything
Q: How do Form and Flux relate to time?

A:

  • Form = structure spanning past/future (what is arranged)
  • Flux = present-only activity (what is happening now)
  • Seam = the temporal aperture where Form meets the present
Q: What is “maximal availability”?

A: The equilibrium state where H=0. The system is simultaneously:

  • Perfectly stable (Form achieved)
  • Perfectly responsive (Flux ready)
  • Idempotent (repetition changes nothing)
  • Ready for infinite extension
Harmony debt columns with H equals debt_coh plus debt_flux ledger panel (HOL-VIS-002)
H = debt_coh + debt_flux — when both are zero, the system is maximally available.
Q: Is this deterministic or probabilistic?

A: The core dynamics are deterministic. Randomness can be introduced at the application layer, but the mathematical guarantees (convergence, idempotence) hold for the deterministic skeleton.


MetaMonism Questions (Universal Embedding & Void↔Everything):

Q: What is “universal embedding”?

A: The theorem that 4QX can wrap (emulate) a broad class of finite systems. For any SmallSystem or SingletonChainSystem with rank ≤ 3, a 4QX holon emulator exists. This is proven constructively.

Q: What systems can 4QX emulate?

A: Currently proven:

  • Any FiniteSystem with reachable states in {s₀, s₁, s₂} (SmallSystem)
  • Any FiniteSystem whose states are pure HF singletons with rank ≤ 3 (SingletonChainSystem)
  • Infrastructure exists for extending to higher ranks (up to k=12)
Q: What is MetaMonism?

A: The property that the void↔everything cycle is scale-independent. Every 4QX-capable universe satisfies MetaMonism, meaning:

  • Void is in the universe and drains
  • Equilibrium representatives drain to void
  • TelosVoid holds (H=0 ⇒ drains)
  • Embeddings preserve these properties
Q: What is “TelosVoid”?

A: The theorem that H=0 events correspond to HF states that are equilibrium representatives and drain to void. This makes “telos = return to void” a formal theorem, not rhetoric.

Q: What is “StrongReabsorption”?

A: The proven property that every equilibrium representative (void, void-equivalent, or pure singleton) satisfies UnionDrain—it has a finite path back to void under iterated union.


AGI Questions (Directions C & D):

Q: How does 4QX relate to AGI?

A: The DualLoopSystem/Constitutional interfaces (Epic 39, SemanticSpine/Core.lean) define what it means for a system to run 4QX dynamics: provide a real step function, a harmony metric H, and prove strict H-descent. The constitutional_converges theorem proves any such system reaches H=0. The five epistemic desiderata in EpistemicKernelRecord define what it means to be epistemically grounded. Together these provide the parametric, type-enforced foundation for AGI alignment.

The legacy flagBundle_holon_and_encodeHarmony_drain theorem (formerly agi_rationality_implies_4qx_dm) was deleted in Sprint 39.5B — its DM conclusions were unconditionally true for any Nat. The real semantic content is in the SemanticSpine (constitutional_converges, constitutional_system_drains).

Q: What is the “rationality kit”?

A: The legacy RationalAGI in Cognitive/Core.lean captures five Bool-flag axioms (H-monotone, seam-only, kernel-init, kernel-preserving, replayable). However, Epic 39 revealed these Bool flags carry no semantic weight — they can be set to true trivially.

The replacement is the parametric DualLoopSystem/Constitutional spine in SemanticSpine/Core.lean, which requires:

  1. h_progress: ∀ s, H s > 0 → H (step s) < H s (strict H-descent as a proof, not a flag)
  2. h_equilibrium: ∀ s, H s = 0 → step s = s (equilibrium fixed-point)
  3. seam_only_holds: SeamOnlyInteraction (constitutional constraint)

You cannot satisfy these by setting a Bool to true — you must provide real proofs about your actual step function.

Q: What is an EpistemicKernel?

A: The legacy EpistemicKernel (Cognitive/Core.lean) was a 3-Bool struct (worldModelConsistent, evidenceBasedUpdating, actionCoherence) with no semantic content.

The Epic 39 replacement is EpistemicKernelRecord (SemanticSpine/Core.lean), which bundles five Prop-level desiderata:

  • TraceableKnowledge: Observed beliefs have source timestamps
  • BoundedClaims: Confidence bounded by evidence status
  • SelfCorrection: Agent tracks H and corrects toward equilibrium
  • EpistemicSeamOnly: All evidence from seam logs (no BL↔BR)
  • EpistemicReplayable: Log is replayable (H-sequence consistent + audit ok)

Each has a corresponding Bool checker with a soundness bridge (via VerifiedChecker).

Q: What is an AGIHolon?

A: A CognitiveHolon wrapped with a BlackBoxDelegate (interface for external models like GPT, Claude, RL agents). Includes query history and compliance checking.

Q: What is AGIRunWitness?

A: An externally verifiable certificate proving:

  • All rationality conditions satisfied
  • The run participates in void↔everything
  • The AGI lives in a 4QX + MetaMonism universe
Q: Can I use this with my AI model?

A: Yes. Implement BlackBoxDelegate with your model, create an AGIHolon, run with compliance checking, and generate AGIRunWitness certificates. See AGI_INTEGRATION_GUIDE.md.


Field Lens Questions (Epic 32):

Q: Is the field really continuous?

A: It’s a dyadic quantised continuum, not true real-valued continuity:

  • Weights are dyadic: Z[1/2] = { k/2^n | k ∈ ℤ, n ∈ ℕ }
  • Refinement is discrete: Depth levels subdivide coordinates
  • Exact arithmetic: No floating-point approximation
  • Deterministic: Same weights → same quanta allocation

Think of it as “continuous-ish”—arbitrarily refinable precision without the nondeterminism of floating point.

Q: Does the field introduce new axioms?

A: No.

  • Field modules are axiom-free: FocusMeasure, FieldWalker, and FieldGO are axiom-free (machine-checked)
  • Interpretive layer has 2 quarantined axioms: name_traversal_is_sus_abstract and unified_interpretation in Pythagorean/Interpretation.lean
  • These are not imported by Prod.lean: The interpretive axioms are isolated

The field operational semantics are fully mechanised; the interpretive programme (reading 4QX as unified QM+GR) is RED.

Q: What’s the difference between field and seam?

A:

AspectFieldSeam
LocationInstance-internalTL↔TR interface
NatureWeighted, refinableDiscrete, replayable
VisibilityPrivatePublic
Character“Continuous inside”“Discrete outside”

The field is where weighted focus lives; the seam is where commitments become events.

Q: What are Pow and Union operationally now?

A: They’re streaming coordinate walkers, not “materialise gigantic sets”:

  • Pow: Salience-filtered expansion via FieldWalker; option scanning with fuel budget
  • Union: Internal structure traversal / aggregation; weighted measure consolidation

Cost grows with visited nodes × depth, not trie size. This makes field operations practical on large namespaces.

Q: What is multiplexing now?

A: Allocate mass across many coordinates, then deterministically clear into discrete quanta.

Old model: Pick one node to process.
New model: FocusMeasure holds weighted distribution; Run phase clears proportionally.


Dyadic and Witness Questions (Epic 31):

Q: Why Dyadic instead of floats / rationals / reals?

A: Dyadics (Z[1/2]) provide the “sweet spot” for 4QX numeric work:

  • Exact arithmetic: No floating-point rounding or nondeterminism
  • Closed operations: +, −, ×, and scaling by powers of 2 stay in Z[1/2]
  • Deterministic: Same value → same quantized result (always)
  • No Mathlib: Self-contained, no external dependencies or axioms
  • Sufficient for limits: Epsilon-delta convergence arguments work with 2^(-n)

Floats introduce nondeterminism. Rationals need GCD normalisation. Reals require Mathlib and axioms. Dyadics avoid all of these while being sufficient for production witnesses.

Q: What is a WitnessBundle and why does production care?

A: A WitnessBundle is the cross-language certificate that accompanies each seam event (quantum). It contains:

  • quantumId: Unique identifier
  • hBefore, hAfter: H values before and after
  • hMonotone, seamOnly, kernelSatisfied, drainCert, replayable: Boolean flags for kernel compliance
  • valid: Overall validity (all checks passed)
  • telos: Instance or Class

Why production cares:

  1. It’s the audit trail for every seam event
  2. The validate() gate ensures only compliant bundles enter the pipeline
  3. It enables cross-language verification (Python runtime ↔ Lean verifier)
  4. It makes H-monotonicity and kernel compliance externally checkable
Q: What does “replayable” mean operationally?

A: A system is replayable if:

Same seam log → Same field state

Operationally:

  1. Every seam event is logged with full context (quantum + state hash)
  2. FieldState.replay(log, precision) reconstructs the state from logs alone
  3. verifyReplay(log, expected_hash, precision) checks the replay produces the expected hash
  4. No hidden state, side effects, or external dependencies

This enables: debugging by replay, audit by re-execution, crash recovery, and distributed consistency checking.

Q: How do I query field state and get an audit trail?

A: Use executeQuery(fs, query, precision):

result = execute_query(field_state, FieldQuery.nodeState(coord), precision)
# result.node         — The node state (localH, coh, flux, etc.)
# result.contributing_bundles  — Hashes of WitnessBundles that affected this node
# result.result_hash  — Deterministic hash of the result for verification

The contributing_bundles field answers “what seam events led to this state?”—essential for audit and debugging.


Implementation Questions:

Q: Can I implement this in [language X]?

A: Yes. The pattern is substrate-independent. The key invariants to maintain:

  1. Four state containers (P, E, R, M)
  2. Six transitions in canonical order
  3. No direct BL↔BR operations
  4. Monotone H reduction
  5. Idempotent seam operations
Q: What data structures should I use?

A:

  • LazyGroup: For P/E/R/M collections (lazy, idempotent)
  • BinaryNode: For trie structure (bit0, bit1, sub, payload)
  • Sets over lists: For idempotence
  • Content-addressing: For deduplication
Q: How do I test for correctness?

A:

  1. Idempotence test: At H=0, verify step(p) = p
  2. Convergence test: Verify H decreases each cycle
  3. Replay test: Verify replaying operations produces same result
  4. No BL↔BR test: Verify no direct path exists
Q: How does this scale?

A: Linearly, because:

  • No global coordination required
  • Operations commute (parallel execution safe)
  • Idempotent merge (no conflict resolution needed)
  • Same pattern at all scales (no architectural changes)

Philosophical Questions:

Q: Does this prove consciousness exists?

A: No. The architecture is consciousness-compatible—it provides structural preconditions (self-reference, world-model, feedback). It doesn’t claim to solve the hard problem.

Q: Is this a theory of everything?

A: It’s a theory of viable organisation—the minimal structure for systems that stabilise and adapt. It doesn’t claim to be fundamental physics.

Q: What’s the relationship to Eastern philosophy?

A: The Form/Flux duality resonates with:

  • Taoist yin/yang
  • Buddhist form/emptiness
  • Vedantic prakriti/purusha

These are noted as resonances, not claimed derivations.

ListenGeometry and Ancient Philosophical Echoes · Diagrams

Geometry and Ancient Philosophical Echoes
Q: Is this claiming metaphysical necessity?

A: No. The proofs show existence within finite ZF, not inevitability. Other constructions are possible; this one has useful properties.

Q: Is 4QX just ZF in disguise?

A: No. The Production Kernel’s characterisation theorem (geom_frag_unique_exact) proves that the binary active geometry forces a unique HF ZF fragment—geometry precedes axioms. 4QX isn’t “using” ZF; the geometric constraints determine which ZF constructors appear and in what order.

ListenHow Empty Sets Force a Dual Engine · Diagrams

How Empty Sets Force a Dual Engine
Q: Does the geometry force ZF, or is ZF just convenient?

A: The geometry forces it. The geom_frag_unique_exact theorem proves that any fragment realising the geometry and compatible with the dynamics is extensionally equal to the canonical [Pow, Sep, Pair, Union, Empty, Repl] fragment. This is uniqueness, not convenience.

Q: What about the “void↔everything” claim?

A: It’s now a theorem, not philosophy. Philosophy/Universality.lean proves:

  • Every equilibrium representative drains to void (StrongReabsorption)
  • H=0 ⇒ equilibrium representative ∧ drains (TelosVoid)
  • The cycle is scale-independent (MetaMonism)
  • Embeddings preserve the cycle

ListenThe metabolic cost of tracking everything · Diagrams

The metabolic cost of tracking everything

Relationship to Other Systems:

Q: How does this relate to CRDTs?

A: The seam essentially implements a CRDT—idempotent, commutative operations with deterministic merge. 4QX provides the theoretical grounding for why CRDTs work.

Q: How does this relate to actor models?

A: Holons are like actors with:

  • Defined message passing (via seam)
  • No shared mutable state (no BL↔BR)
  • Guaranteed termination (H→0)
Q: How does this relate to category theory?

A: The six ZF constructors can be viewed categorically (Power as contravariant, Union as colimit, etc.), but the formal proofs don’t require category theory.

Q: How does this relate to thermodynamics?

A: H acts like entropy in reverse—it strictly decreases toward equilibrium. The system is a dissipative structure that maintains local order by processing flux.


Troubleshooting:

Q: My H isn’t decreasing. What’s wrong?

A: Check for:

  1. Hidden BL↔BR paths
  2. Non-idempotent operations
  3. Wrong phase ordering
  4. Missing debt accounting
Integrate and Publish as debt-reducing return edges with gap table (HOL-VIS-002)
Integrate closes the flux gap (TR→BL); Publish closes the coherence gap (BR→TL).

ListenWhen tension actually clears · Diagrams

When tension actually clears
Q: I’m getting non-deterministic results.

A: Ensure:

  1. Seam operations are truly idempotent
  2. Fold-back functions are pure
  3. No hidden state outside P/E/R/M
  4. Consistent ordering (if using lists)
Q: Composition isn’t working.

A: Verify:

  1. Seams are properly aligned
  2. No cross-composition BL↔BR
  3. Parent H = sum of child H
  4. Idempotence preserved at each level
Q: My AGI isn’t compliant.

A: Check AGIHolon.checkCompliance() for which property fails:

  1. Kernel: Does the cognitive holon satisfy epistemic desiderata?
  2. Seam discipline: Are all events seam-only?
  3. H-monotonicity: Is H non-increasing?
  4. Replay: Is state deterministically reconstructible?

Where to Learn More:

For the Formal Proofs

See the Lean 4 code:

  • Kernel: Geometry, Phase, Fragment (characterisation)
  • Philosophy: Pythagorean, Rotation, Universality (MetaMonism)
  • SocialContract: Constitutional kernel and guarantees
  • Cognitive: AGI rationality integration

For Conceptual Understanding

Start with files 01-05 in this compendium

For Implementation Guidance

See file 16 (Implementation Tech)

For Philosophy

See files 12 (Dialectical Monism) and 13 (Cognitive Substrate)

For AGI Integration

See SocialContract/Cognitive/Discussion/direction-c/AGI_INTEGRATION_GUIDE.md


One Last Question:

Q: Why should I care about 4QX?

A: Because it provides:

  1. Formal guarantees about system behaviour
  2. A universal pattern applicable across domains
  3. Practical architecture for distributed systems
  4. Philosophical grounding in dialectical monism
  5. A path to aligned AI through structural constraints
  6. AGI integration (Epic 39: legacy hollow theorems deleted; replaced by constitutional_converges in GapMap.lean and DualLoopSystem/Constitutional in SemanticSpine/Core.lean)

In a world of ad-hoc systems and untested assumptions, 4QX offers a foundation you can prove things about—and for AGI systems, that proof includes externally verifiable certificates.

More diagrams: [Diagrams](/diagrams/) · More audio: [Podcasts](/podcasts/)

Class and Instance triangles sharing the public seam; no Resource–Metric shortcut (HOL-VIS-002)
Two lifecycles — Class and Instance — share the public seam only.
Clockwise numbered operator cycle starting at 1 Fit: Fit, Offer, Accept, Run, Publish, Integrate (HOL-VIS-003)
Generic Organisation cycle for operators — clockwise from Fit.