docs: clarify AFS macOS consent result - #52
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies the documentation around the experimental AgentFS macOS loopback NFS mount result, distinguishing a successful human Terminal validation from the still process-/client-specific macOS privacy (TCC) consent requirements.
Changes:
- Updates architecture docs to reflect that a human Terminal validation passed and that per-process macOS consent is still required.
- Rewrites the Agent filesystem page to record the 2026-08-09 human Terminal mount/read/write validation and clarify client/harness-specific consent implications.
- Adjusts daemon security posture docs to reflect the validated behavior while reiterating remaining safety/access-control gaps.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| content/docs/guide/architecture.mdx | Updates the architecture overview to reference the passed human Terminal validation and remaining per-process consent requirement. |
| content/docs/guide/agent-filesystem.mdx | Records the human-operated macOS validation steps and updates the roadmap gating language around consent and remaining unknowns. |
| content/docs/daemon/security.mdx | Clarifies security posture wording: validation was for one consented client, while other processes may still be denied. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| | Storage foundation | Shipped experimental | `coven-afs` provides the SPEC-compatible schema, filesystem operations, and copy-on-write overlay. | | ||
| | macOS NFS and performance spike | Shipped experimental | A feature-gated NFSv3 export and benchmark show a conditional storage-engine GO with WAL. Agent-process confirmation, concurrent-client evaluation, and Linux/FUSE remain open. | | ||
| | Mount safety decision | Planned after spike | Resolve loopback access control, default-off behavior, copy-up limits, base-ingest filters, platform-specific recovery, and the macOS privacy confirmation before enabling any mount by default. | | ||
| | macOS NFS and performance spike | Shipped experimental | A feature-gated NFSv3 export and benchmark show a conditional storage-engine GO with WAL. Human Terminal validation passed; the result requires a client-/harness-specific macOS privacy or network-volume access assessment, while concurrent-client evaluation and Linux/FUSE remain open. | |
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.
Summary
Validation
pnpm run buildpnpm run check:linksgit diff --check