VELMAFORGE
The Quiet Forge VELMA. Proof and strike. Retained.
A paired-kernel architecture.
VELMA is built as two kernels that do different work in different registers. They are designed to be honest about what each can claim and what each cannot.
The Anvil
S is the static kernel. Written in Haskell and Fortran, where the type system and the explicit-numerical register mean a claim is either total or it is wrong; there is no third state.
S accepts what S can verify. It does not negotiate.
-- drift is a type error, not an exception. data CanonRule :: CanonStatus -> Type where RVELMARetained :: CanonRule 'MustNotDrift RProofRequired :: CanonRule 'Settled
The Hammer
D is the dynamic kernel. Written in Python, Rust, and TypeScript, where the work happens against the world: data arriving, models running, decisions made under time.
D produces what D can produce. It does not pretend stillness.
# live-contact: produce, mark, hand off. async def strike(input: Signal) -> Artifact: artifact = await model.run(input) artifact.mark("verifiable") return artifact # to whom?
An open question, by design.
When D produces output that S must absorb, who initiates verification? The Studio has not yet ratified the protocol. The question is open because the answer is load-bearing.
“Who initiates verification when D produces output S must absorb?”
D-initiated. D, knowing it produced something verifiable, hands the artifact to S with a verification request. S accepts or rejects; D either marks the artifact verified or quarantines it. D drives the rhythm; S responds.
S-initiated. S, watching D's outputs at a known interface, pulls artifacts and verifies on its own clock. D does not wait; S catches up. S drives the rhythm; D produces freely.
Retained, by doctrine.
VELMA is retained Studio IP. No partnership, license, assignment, or technical transfer is in force. The Quiet Forge lane is the originating intellectual lane and is not bridged to other lanes by doctrine.
The hashes any extension must pin.
Per the BNS/pd9 AI Citation Standard. Future agents extending the VELMA stack must reference one of these anchors, or be treated as drifting by doctrine.