b799af5beaifc-fides (review by @JoannaaKL): - confidentiality is public/private only on the wire; drop the reader-list (logins aren't uniform across servers, are themselves access-restricted, and reader sets can be huge) - add Reader-set resolution section: two private markers aren't equal, the confidentiality join is the intersection and isn't computable from opaque wire markers, so hosts resolve to concrete reader sets at decision time - integrity join is total/wire-computable; confidentiality join is not - emitter MUST classify per resource, not per repository (public repos serve non-world-readable sub-resources), making github-mcp-server a real proof point action-metadata / docs: - SEP-2061 closed 2026-06-13 in favour of this extension; this draft is now the canonical home. Updated action-metadata.mdx, README, sep-disposition, related-work, and intent-comment status accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2.8 KiB
2.8 KiB
Related work
External references and prior art relevant to the IG's trust / privacy annotation work. Several were surfaced in IG meetings (notably 2026-05-28).
SEPs
- SEP-1913 — Trust and Sensitivity Annotations — the umbrella proposal these extensions derive from.
- SEP-2061 — Action Security Metadata — closed 2026-06-13; carried forward as
action-metadata. - SEP-1862 — Tool Resolution / pre-flight checks — core-protocol, composes with these extensions.
- SEP-2133 — Extensions — the framework this repo incubates under.
- SEP-2127 — Server Cards — precedent for the Standards→Extensions Track refactor.
- SEP-2787 — Tool Call Attestation — candidate
evidenceRefprofile.
Research
- FIDES — Information-flow control for LLM agents. arXiv:2505.23643. Basis for the
ifc.fides.v1profile. - Design Patterns for Securing LLM Agents — IBM/Google/Microsoft. arXiv:2506.08837. Plan-Then-Execute, Dual LLM, Map-Reduce, etc.
- Trail of Bits — prompt-injection via hidden content in GitHub issues. blog.
- OpenAI Auto Review — https://alignment.openai.com/auto-review/ (shared in IG chat).
Implementations & tooling
kapil8811/mcp-trust-annotations— reference Python SDK PoC fortrust-annotations.github-mcp-server— public MCP server; emitter candidate forifc-fides(knows repo visibility + collaborators).- Ethyca data-labeling docs — https://www.ethyca.com/docs (shared in IG chat).
- GitHub Next agentic-workflows research on data labeling — to be documented as issues in this repo (IG action item, @gokhanarkan / @joannakl).
Adjacent community proposals (from the SEP-1913 thread)
- SINT Protocol (capability-token constraint enforcement) — pshkv.
- in-toto attestations as a trust-annotation substrate.
- OVERT 1.0 envelope shape for runtime evidence.
- Caller/tool cosigning model — viftode4.
- Sequence-shape policies — marras0914.
These are exactly the models that evidenceRef's open type is designed to
accommodate as profiles.