docs: nominate governed knowledge substrate research venue

[coreytshaffer]

Scope

Exactly one new documentation file. 222 insertions, zero other changes.

• Added: docs/research/candidates/governed-knowledge-substrate.md
• Not touched: docs/current_backlog.md, docs/futures/futures_register.md, docs/change/change_log.md, and everything under triage_core/, schemas/, tests/.

What this records

GBrain is nominated as a venue candidate: an adjacent application proposed as an external test instrument for existing TriageCore governance semantics. It is neither part of the governance kernel nor an approved TriageCore knowledge subsystem.

Core hypothesis under test: retrieved knowledge may influence reasoning, but must not confer, expand, or consume executable authority.

The document defines four operations (read / stage-write / canonical-write / delete), five adversarial cases, four research questions, and an existing-vocabulary test that names both the primitives to try first and the primitives that must not be introduced on the strength of this candidate.

Deliberate constraints

• Un-numbered. No EXP- namespace is opened. Identity is assigned by the repository's CR- promotion process at promotion, if it happens.
• Registers nothing. Placement in futures_register.md, Candidate Future Work, or both — and the canonical relationship between those registries — is a separate decision deferred until the open evidence window closes. The document says so, so the absence is not read later as an oversight.
• Repository recorded, commit unpinned. No commit has been evaluated. Current HEAD is explicitly not substituted; a pinned evaluated commit is written into the entry criteria instead.
• Gated. No experiment is authorized until the daily-use evidence window is complete, results recorded, open questions resolved or characterized, conclusions frozen, a commit pinned, and the experiment separately approved. The gate is methodological: adding knowledge-specific events, capability types, provenance fields, or executor semantics while the window is open would make any behavior change ambiguous between the system under test and an architecture evolving underneath it.

Claim boundaries

This document grants no implementation, integration, schema, execution-expansion, configuration, branch, merge, or standing authority. It is not evidence, not approved architecture, not a backlog item, and not part of the evidence window. It makes no claim that TriageCore can govern an external knowledge substrate, and no claim about the candidate system's safety or suitability. Nothing in it reflects source inspection of the candidate repository.

Two notes exist specifically to prevent later misreading:

• The replay/double-consume adversarial case carries a lineage note — CR-OC-001A classifies replay without preventing it, and CR-OC-001B exists as an unconsumed library surface — so an implemented contract is not collapsed into an enforced one.
• Results from any future experiment must be reported on both axes from the NVIDIA containment analysis (mechanism maturity, live-path enforcement) rather than as a single label.

Verification

Check	Result
git diff --cached --stat	1 file changed, 222 insertions, 0 deletions
git diff --cached --check	no whitespace errors
git status --short	single A entry, no residue

Tests not run: no executable, schema, or test surface changed.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for poetic-quokka-0fd859 ready!

Name	Link
🔨 Latest commit	d5fda48
🔍 Latest deploy log	https://app.netlify.com/projects/poetic-quokka-0fd859/deploys/6a76a99bc4d356000868e036
😎 Deploy Preview	https://deploy-preview-152--poetic-quokka-0fd859.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.