Filesystem grants spike
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 152
- Forks
- 16
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 536
Description
User story
As an adopter, I want the harness to hold its own workload identity and the people using it to hold theirs, so that one deployment can serve many users and every action still traces back to a person.
Acceptance criteria
- In-process issuer: dual-TTL, audience-bound grants; renew/close/decline
- memfs-backed filesystem service: streamed reads, server-side glob/grep, per-verb enforcement, the three postures, conditional writes
- Byte-sink service (keeps the generic envelope honest)
- PDF scenario end-to-end (bytes never transit the harness)
- Conformance probes: every verb against every posture
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.