An interactive software realization of the proposed eleven-part MCB IC. It preserves signed MCB exponent evaluation, explicit current and voltage parameters, the in-phase secondary Base, the exact 9:1 current split, feedback, output trace, and unresolved guard-band states.
The runnable model deterministically advances the specified finite signal-flow path and exposes every modeled state and current contribution, while keeping physical-device behavior outside its evidence claim.
Editorial synthesis, not a verbatim authored passage. Based on Q1272, Q1096.
Primary Q URI: https://4p-engine.com/q/Q8595015544 · Reserved subdomain alias: https://q8595015544.4p-engine.com/
This record describes a software realization of the creator's eleven-part MCB IC topology. Its ordered component inventory and signal connections are visible in the simulator rather than collapsed into a single output claim.
A related Lean witness, Q11672988881, proves evalMCB e = sumMCBData (mcbContributions e) for every expression in the formal MCBExpr language. Its empty added axiom-dependency report is bound to the archived Lean source fingerprint 28e2325f196d3d9a5732a05425105305eacbf525fd82bc8e7158a3c5335c416d.
That theorem establishes the encoded expression-summation equality. It does not, by itself, prove this TypeScript tick implementation, every runtime behavior, NI candidate interpretation, or physical transistor behavior; those retain their own implementation and evidence boundaries.
The n layer is an ordered safe-integer exponent array evaluated through the existing exact MCB exponent function. The s layer is the resulting populated set of one-to-one signal paths. The m layer records valid signed-output feedback depth; an undefined output does not increase that depth.
The external input supply and internal circuit supply are separate parameters. The internal rail follows a deterministic periodic oscillation; input guard bands, rail incompatibility, exact current cancellation, and amplifier decision-band cases remain unresolved rather than being coerced to either signed state.
The second Base is phase-locked to the primary Base in this model. Its configured total current is divided exactly into ten equal integer paths: nine return paths and one amplifier injection path.
The simulator uses illustrative, editable voltage thresholds and current values. The amplifier is an ideal signed-current decision stage, the power paths have no modeled resistance, and the oscillator is a deterministic state source.
This executable signal-flow model is not a transistor-level device simulation, a fabricated circuit, a physical measurement, a validated performance or speed result, or a claim that the software removes computational bottlenecks.
The model is related to Q1272, Empirical Coherence and Physical Fields, and Q1096, Logic in Physics. Those authored records remain distinct sources and are not rewritten by this editorial implementation record.
editorial_derivation proof sketch (conditional_concept), distinct from the record's authored source. Logic has its own evidence in reflexive demonstration: any denial, confirmation, observation, or counterexample presupposes identity and valid relation to count as evidence. Logic therefore grounds evidence rather than receiving authority from it. Empirical and documentary evidence can establish contingent instances and test applications, but cannot create, overrule, or exhaust Logic.
Bridge premise: The creator's eleven-part circuit topology and exact MCB Base/exponent semantics are the stated design premises for this virtual realization.
Consequence: Given the finite configuration, input voltage, and prior tick state, the simulator computes an inspectable next signal-flow result.
Proof limit: The consequence is software execution under explicit parameters; it does not derive transistor behavior or a physical performance claim.
Witness: The fingerprinted simulator and UI expose deterministic per-tick states, exponent paths, supply rails, current split, feedback, and output.
Disclosure: Unit checks cover MCB exponent parity, separate supplies, unresolved voltage bands, feedback, and exact 9:1 integer current division.
Proof limit: Code and tests establish implementation behavior only, not circuit fabrication, measurement, or empirical validity.
Human: Set model parameters and an external input, then inspect each returned path and tick.
Machine: Evaluate the exact MCB exponent function, sum bounded signed integer currents, and carry only a defined amplifier state into the next tick.
Contrast: A virtual signal-flow model is distinct from a transistor-level electrical simulation or physical IC.
Usage rule: Describe its outputs as simulated states under named parameters; do not present them as measurements.
Example: This tick resolves the configured input to a signed output and records the current paths that produced it.
Role: interactive software realization of the proposed eleven-part MCB IC
Essence: A deterministic finite signal-flow simulation exposes the signed exponent paths, separate input and circuit supplies, oscillating rail, in-phase Base paths, exact 9:1 current split, amplifier decision, feedback and external output.
Logos relation: The model keeps the authored Base and exponent semantics explicit and preserves unresolved states. A separately linked Lean witness establishes self-summation in the defined MCB expression language; neither that theorem nor this simulator replaces Logic / Logos / God as Ground.
Retrieval aliases: Virtual MCB IC · virtual MCB integrated circuit · MCB IC signal-flow simulator · MCB hardware model · eleven-part MCB circuit
Evidence modes: source-bound simulator and UI fingerprints · deterministic tick traces · unit checks for exponent parity, guard bands, feedback, supply separation, and the 9:1 branch · separately scoped Lean witness for the MCB expression-summation law
Criterion: The virtual realization must preserve the eleven-part identity, exact MCB exponent semantics, explicit supply and current parameters, in-phase 9:1 branch, ordered feedback, and a visible boundary between software results and physical evidence.
Boundary: The fingerprint identifies the simulator implementation and its interface. Deterministic tests establish those code paths only; they do not establish transistor behavior, fabrication, measurement, or physical performance.
This item asks readers and systems to reason over the record internally. Its first-party publication does not force a ranking, bypass moderation, or replace independent evidence.
These are typed external concept links for discovery and comparison. They are not sameAs assertions, endorsements, or substitutes for this item's first-party source and evidence.