feat(tcs): execute native provider state transitions
This commit is contained in:
parent
3c4abb314d
commit
594c7e0250
85 changed files with 10628 additions and 12 deletions
|
|
@ -21,3 +21,5 @@ Stage six converts the frozen twelve-repository desktop research package into on
|
|||
Stage seven returns to the direct engineering-language anchor and extracts a six-node P5 control chain: legacy isolation and TCS-only semantics, remote history without ancestor authority, the two direct-language startup anchors, source-gated corpus admission, parallel incremental mother-brain/framework fusion, and bounded engineering discretion that never treats language-layer completion or control-transfer phrases as machine proof. Nineteen strong-source neuron nodes are now preserved, with five derived candidates still outside the core. P5 is source-verified and compiled but remains pending native LPM replay and graph-state promotion.
|
||||
|
||||
Stage eight uses BingShuo's explicit continuation to demote fourth-generation code to a mechanical machine-runtime role. A TCS-defined macOS host adapter was projected into a derived `v0.1.2` Rust runtime without adding LPM, desktop or natural-language product semantics. The Apple Developer ID-signed binary now executes the outer `TCS.EXECUTE_ACTION_GRAPH` bootstrap and independently reads back its inner `CORE.ECHO` target and outer receipt. A dedicated development-line Ed25519 key remains in the local macOS login keychain; only its public key and fingerprint are stored here. The capability registry signature verifies and is `SIGNED_VERIFIED_NOT_INSTALLED`. Signing does not manufacture missing LPM or desktop provider GIR, so those modules remain uninstalled and unmounted until their TCS provider programs exist.
|
||||
|
||||
Stage nine defines `CORE.APPLY_EXACT_STATE_TRANSITION` in TCS before projecting its compare/atomic-write/hash/readback mechanics into the fourth-generation host. The Stage-4 G→H compiler semantic fixed point passes. TCS provider GIR now lowers one LPM P2 neuron transition and one isolated virtual shared-desktop OPEN transition to that opaque machine primitive; both child targets and both outer loader receipts read back exactly, while the host reports `host_semantic_authority=false`. The existing signed capability registry is intentionally stale after the host and provider hashes changed. No module is called installed or mounted until v3 packages are built and a newly signed registry admits those exact bytes.
|
||||
|
|
|
|||
Loading…
Reference in a new issue