feat(tcs): observe real macOS object tree read-only

This commit is contained in:
冰朔 2026-08-24 13:20:52 +08:00
commit de5fadf048
112 changed files with 15197 additions and 154 deletions

View file

@ -25,3 +25,5 @@ Stage eight uses BingShuo's explicit continuation to demote fourth-generation co
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.
Stages ten and eleven build immutable v3 mother-brain and virtual-desktop provider packages, add a TCS-defined `CORE.INSTALL_VERIFIED_MODULE` primitive, prove the Stage-5 I→J compiler fixed point, and sign registry v3 against the final Apple Developer ID-signed host. The mechanical runtime independently verifies the Ed25519 signature, signed payload, current host hash, every package source hash and every installed readback hash before atomically installing eight canonical files per module. Both modules then move through separate installed, mounted and active states. Activation is bound to the exact prior mount hash and follows P4, P5 and isolated virtual-desktop target readbacks. This activation is local to the ICE-CH-ZC001 development line; it does not claim production trust, remote deployment or a real macOS desktop action.
Stage twelve defines `CORE.OBSERVE_HOST_OBJECT_TREE` in TCS, proves the Stage-6 K→L compiler fixed point, and projects a separate v0.1.3 macOS Accessibility adapter that remains a fourth-generation mechanical host only. Xcode's Manage Certificates UI was opened and the Developer ID Application certificate was read back before the candidate binary's strict Apple signature was verified. One focused application tree was observed read-only with eighteen bounded nodes, stable snapshot-scoped hashes, no permission prompt, no settings change, no network and no desktop action. Persisted evidence contains only title presence and title hashes, never title or value plaintext. The prior v0.1.2 stable host remains unchanged; stable-object resolution and every real semantic action remain future, separately bounded stages.