Sushii Sourcing · The Neural Spine
Sushii Sourcing preserves governed documents, references, and exact revisions so connected products can rely on the right source without collapsing their authority into one system.
The human problem is drift.Policies change. Prompts change. Agreements change. Source material changes. Without stable identity and provenance, people and systems can act on stale or contradictory versions without realizing it.
The private Neural Spine runtime is established for bounded reads. The Sourcing browser workspace remains a separate product surface.
The problem
Sushii products should be able to answer: What object is this? Which exact revision are we using? Where did it come from? What changed? Who is allowed to read it? And does the downstream product actually have authority to act on it?
The Neural Spine response
Preserve the governed memory once, then let each sovereign product consume only the exact material it is authorized to use.
Three kinds of governed memory
Sourcing gives them shared revision and provenance mechanics without flattening their meaning. An external legal source remains external authority; a Sushii architecture contract remains a governed internal contract; an experiment remains evidence until something adopts it.
Governed contracts
The Contract Library keeps stable identities, immutable revisions, exact digests, proposal lineage, and provenance for governed Sushii contracts. A product can pin the exact revision it uses without becoming the contract authority.
External references
The Reference Library keeps exact captured source identity, revision, provenance, and normalized retrieval material. A statute, case, standard, rule, or other external source remains a reference; storing it does not turn it into a Sushii-authored contract.
Research custody
Research evidence can be preserved with its methods, source artifacts, and lifecycle state so later systems can tell the difference between a recorded experiment, an indexed source, and an adopted product decision.
Authority stays explicit
Sourcing is canonical for the governed objects it owns. That does not make it the legal decision-maker, commerce system, executive reasoning engine, presentation authority, or universal permission layer.
How connected products use it
Brain can assemble authorized Spine context. Mind can reason over it. Tsugiita can explain it to a person. Legal can pin a managed agreement revision. Deck can render an authorized source revision. Each consumer remains responsible for its own permissions and effects.
Sourcing records stable identity, immutable revision, digest, provenance, and lifecycle state.
The Sourcing boundary verifies the requesting subject, product instance, and capability before protected reads.
The downstream product receives bounded, revision-pinned context and still applies its own authorization and domain rules.
Current product state
Sushii already has a private, authorization-gated Sourcing runtime for bounded governed reads. The next product step is a read-only operator experience for inspecting libraries, exact revisions, provenance, and consumer status—not exposing private runtime routes directly to the web.