feat(tcs): ignite generic host and signing trust
This commit is contained in:
parent
3049cbb458
commit
3c4abb314d
26 changed files with 2655 additions and 0 deletions
|
|
@ -19,3 +19,5 @@ Stage five applied that gate to the first five-event chain and failed it closed:
|
|||
Stage six converts the frozen twelve-repository desktop research package into one TCS-native framework behavior contract. No upstream project is selected as HoloLake and no old-language product source is imported. The framework is the TCS protocol itself: observe one structured object tree, resolve one snapshot-scoped stable object, authorize one exact semantic action, execute, reobserve, read the state diff, verify the declared effect through independent target readback, and only then issue a receipt. Dispatch success, process exit, screenshots and pixel coordinates are not effect proof. The protocol and its bilingual projections compile under the Stage-3 fixed-point compiler; desktop execution remains pending the generic GIR action-graph machine primitive, signed capability registry, module installation and mounting.
|
||||
|
||||
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.
|
||||
|
|
|
|||
Loading…
Reference in a new issue