feat(tcs): adjudicate sources and replay language-world chain
This commit is contained in:
parent
a826e6eb78
commit
385a9f52fc
23 changed files with 2198 additions and 10 deletions
|
|
@ -13,3 +13,5 @@ Stage three adds a TCS-defined generic action-graph loader ABI and `TCS.EXECUTE_
|
|||
The current boundary audit proves why the outer loader is not yet runnable: the available machine runner accepts exactly one action and dispatches through a fixed host operation table. TCS compiler registration changes language admission but does not add a machine primitive. The next physical dependency is one generic TCS GIR action-graph executor whose host carries no natural-language or operation-specific product semantics, followed by a separately authorized Ed25519 signer registration. Until both are read back, the three module packages remain verified but uninstalled.
|
||||
|
||||
Mother-brain corpus admission now has an explicit TCS source gate. A transport `user` role is not author proof; host injection, pasted model output, persona-derived pages, language-world simulation and unverified embedded quotes cannot be promoted as direct BingShuo language. The first new five-event correction chain preserves the original text hashes separately from the rebuildable interpretation graph and remains provisional until the original rollout envelope and native LPM replay both pass.
|
||||
|
||||
Stage five applied that gate to the first five-event chain and failed it closed: two derived copies agree byte-for-byte, but the original laptop rollout is unavailable and the task-service readback returned an upstream access challenge. The candidate graph is preserved without core promotion. Work continued from the stronger current direct-language anchor instead, producing a seven-node contiguous chain from the bidirectional translation gap through language-world growth, mother-brain/library separation and bounded Agent TCS brains. Its minimum `CORE.ECHO` replay has executed with target readback; this is evidence of bounded TCS replay, not native LPM graph execution.
|
||||
|
|
|
|||
Loading…
Reference in a new issue