Carry interactive Gemini identity and trust state - #4
Closed
mark-ik wants to merge 5 commits into
Closed
Conversation
…ld not A1 landed, so there is finally something real to render: unmet_holds crosses the wire, honored_holds names the satisfied pins, and the frozen realization already lists violations in its tabular alternate and announces them in its AccessKit tree. Cambium cannot render any of it. It has no sceno dependency, so it cannot see a Scene, and nothing in mere consumes cambium either. Both directions checked against the tree rather than assumed. This is Track C arriving at the correction Track B already took. A host renders into cambium's surfaces; the code that knows what a hold is lives mere-side. So C1 needs a mere-side host built on cambium, and none exists, which is the same absence that blocks a driven probe scenario. mer3ly could take it now without a new host, since it already reports a honored count on its export control and the snapshot now carries the violations alongside. That is C1's substance in a web page rather than native chrome, and it costs a rev bump, a wasm rebuild, and a public deploy, so it is a decision rather than a quiet extension of this target. What is deliberately not built: a cambium surface with no consumer. That is the work five gated targets are being held back from, and adjacency to something that just landed is not an exemption.
The plan recorded the first attempt's apparent event-loop hang as a genet-side defect. It was not one: the run was waiting on a macOS permission prompt on the machine's own screen, invisible to the driver. Accepting it and re-running the identical command passed, with 3 frames, 0 blank, 3 distinct digests. Kept as a lane property rather than an anecdote, since it will recur: a headed run on macOS can block on a prompt the driver cannot see, so a first run there wants someone at the screen and a hang is a prompt until ruled out.
…shell The 2026-07-23 repo consolidation archived graphshell, and that repo's whole design_docs tree is deleted at HEAD, so its 633 donor docs survive only in git history. Eight of them were federation, distributed-index, and storage-economy research that no mere doc carried: the 2026-05-27 full harvest summarizes VGCP in a single table row, and the other seven were never indexed at all. Five landed in the previous commit's sweep. This finishes the set. New here: - 2026-02-27_freenet_takeaways_for_verse (04d6836): split shared-state logic from private-identity logic, keep capability surfaces narrow per provider. - 2026-03-28_libp2p_nostr_synergy_for_verse (f36fc49): names the control plane / data plane split, where Nostr carries small signed events that reference CIDs and libp2p delivers the bytes behind them. Carries the donor's repo-wide MPL-2.0 notice verbatim, which is worth a look against this repo's MIT/Apache posture. - 2026-02-04_donor_docs_search_findings_summary (04d6836, donor filename SEARCH_FINDINGS_SUMMARY.md): a ten-topic survey of 27 donor docs, kept for its decision record rather than its mostly dead links. Dated from its own date line. Repaired: 2026-02-23_storage_economy_and_indices was committed as an empty file; it now has its content. DOC_README gains a Recovered donor research block covering all eight, and its inheritance section now records that a local archived clone sits at Code/archive/graphshell with the rest still reachable through history, fullest tree at 401e2fc. Every recovered file carries a provenance header naming its donor path and source commit, and saying plainly that none of it was ever implemented. It is filed as research, not as direction, and it speaks the retired Verse vocabulary. Deliberately left out of this commit: two technical_architecture docs carrying another agent's in-flight subgraph-to-nested-graph terminology edits.
mark-ik
changed the title
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Depends on merely-made/genet#2.
Verification