Skip to content

Add a completeness fence over the GraphQL mutation surface #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
beardthelion wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Add a completeness fence over the GraphQL mutation surface #219

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a2a03b7
test(node): add a completeness fence over the GraphQL mutation surface
beardthelion Jul 18, 2026
b948f21
docs(node): reconcile GraphQL mutation-auth claims with the shipped s…
beardthelion Jul 18, 2026
d979d0e
fix(node): source the GraphQL mutation fence from SDL, not introspection
beardthelion Jul 22, 2026
31d7f27
fix(node): make the SDL mutation-fence wiring load-bearing; admit dep…
beardthelion Jul 22, 2026
37e022d
fix(node): rebase #219 and require signer gate in the GraphQL fence
beardthelion Aug 30, 2026
14dae89
docs(node): reconcile GraphQL fence docs with SDL discovery
beardthelion Aug 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Known limitations:
- Agent lifecycle revocation is not enforced by HTTP Signature authorization; do not rely on removing or revoking an agent record to block a compromised signer.
- Read visibility is not a blanket data-classification boundary: task, IPFS-pin, and Arweave-anchor listings are not repository-gated; withheld path names can be visible to a root reader; and later visibility changes cannot retract content already announced or externally anchored.
- Peer writes are signed by upgraded nodes, but strict signed-peer enforcement is opt-in during rolling upgrades.
- Current GraphQL mutations require an authenticated signer, but there is no mutation-specific guardrail that prevents a future mutation from omitting that check.
- GraphQL mutations require a signed identity (a verified signer bound to the acting DID), are limited to the agent-task queue, and are covered by a CI completeness fence that requires signer acquisition and actor binding on every registered mutation; repo writes are not exposed over GraphQL and remain REST-only.
- Pull-request review comments do not yet have threaded line-level anchors, and merges do not enforce approval requirements.

See:
Expand Down
Loading
Loading