feat(browser-evidence): add governed evidence authority - #184
Draft
yaacovcorcos wants to merge 10 commits into
Draft
feat(browser-evidence): add governed evidence authority#184yaacovcorcos wants to merge 10 commits into
yaacovcorcos wants to merge 10 commits into
Conversation
…feature/scient-browser-evidence-authority-b0
Contributor
Author
This was referenced Aug 1, 2026
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
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.
User effect
Adds the production-dark authority kernel needed for future browser-assisted scientific evidence work. The kernel can bind a bounded browser operation to the exact actor, project, provider thread/turn, tab, document, navigation, and document digest; record digest-only source provenance; create annotation/proposal/verification receipts; and reserve accept, reject, and export decisions for an explicit manual user action.
This PR does not expose a browser, transport, server route, UI, persistence adapter, publication path, or live-data integration. It is a separately governed architecture-foundation lane, not a claim of live-product readiness or a small fast-lane feature.
Provenance and disposition
Scient-native reimplementation inspired by these Synara concept commits:
8f6521a67b77a849febef920e96e57acbfc89335e3850b69cb55ee4fdb709a3bce9ee0e185732c6cc67ccc72326a7e7351b998033a0f3b524b156e64f16bda8efde8e1fc1e3b0a7c4e3e543d3145efe7No donor source was copied. The repository's root MIT notice remains applicable. The design deliberately excludes Synara product identity, persistence, browser transport, publication authority, and automation truth semantics.
Exact scope
6d5530f8a19b001d0e3f0e6cfd8156bf20ded926(feature/scient-automation-operation-authority-a1)161b9b151560967189c794977871b196d8ed7d7eapps/server/src/browserEvidence/authority.ts,contracts.ts,PROVENANCE.mdapps/server/src/browserEvidence/authority.test.tsProtected decisions:
Review repair
The defensive scan reproduced a cross-document annotation bug on the pre-repair head: a source receipt from one document could be paired with an annotation lease for another document within the same project/thread. Commit
161b9b151repairs this before operation replay consumption or receipt append by requiring exact source-document equality. The regression proves matching success plus independent tab, document, navigation, and digest mismatch rejection.Verification
bun run fmt:check: passedbun run lint: passed with no errors; existing repository warnings remain, including one intentional sparse-array test warning in this lanebun run test: 12/12 tasks successful; CLI 2,873 passed and 10 skippedgit diff --check: passedNo computer use, browser automation, screenshots, geometry checks, visual tests, visual regression, or manual UI acceptance were performed.
Independent final reviews
Exactly three non-author reviews certified head
161b9b151560967189c794977871b196d8ed7d7ewith no unresolved P0, P1, or P2 findings:The architecture review explicitly classifies this as a separately governed production-dark foundation, not ordinary fast-lane product work.
Rollback and limitations
Rollback is removal or revert of the four isolated browser-evidence files; no migration, live state, credentials, transport, or user data is involved.
Before any live composition, a later governed lane must add durable storage with atomic compare-and-set behavior and bounded retention, host-attested digests from captured bytes, canonicalization depth/cycle bounds, and restart/concurrency proof. The host-only lookup/revocation surface must remain unexposed. This PR provides no live browser behavior by itself.
Dependency status
Depends on draft PR #182, which in turn depends on the existing operation-authority stack. Keep this PR draft and stacked until its bases are reviewed and integrated in order.