ACL zones: zone-based rights, implicit creator write, agent-keyed discovery

[joepio]

Summary

ACL zones, agent-keyed pkarr discovery, DID open/share hints, and related planning (atomic: URI rename remains planning-only).

CI chase (resolved)

1. e2e oxlint padding + pre-commit oxlint --fix
2. data-browser oxfmt on DID open / overlay files
3. Dagger mount for testdata/resolve-agent-response.json
4. Auth: check_append no longer falls back to write on the new child (implicit creator write hole). Append only on zone(parent) per planning/zones.md.

Benchmarks (zones PR vs develop)

New Criterion suite: cargo bench -p atomic_lib --bench rights_bench --features db-redb.

Same machine, --measurement-time 5. Public-deny path (must walk ancestors) is where depth hurts:

check	depth	develop	zones PR
check_read public deny	10	1.09ms	0.60ms (~1.8×)
check_read public deny	25	2.76ms	1.32ms (~2.1×)
check_read public deny	50	5.54ms	2.46ms (~2.3×)

Owner allow stays ~2µs on both (already O(1) via drive stamp / creator short-circuit). Create-200 and width-1000 are within noise (~same / ~1.09×). Shallow public deny (depth 1) is slightly slower on zones. Remaining O(depth) on deny is zone derivation walking parents — the persisted zone index in planning/zones.md is still TODO.

Status

Main (Mancave) CI was green on 64cb145f; rights_bench added after.

Test plan

• Local unauthorized/authorized COMMIT sync + hierarchy/zones + drive_rights
• CI Main (Mancave) green
• Criterion rights_bench vs develop worktree

  

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26549932	Triggered	Generic High Entropy Secret	02abcda	lib/src/discovery.rs	View secret
26549932	Triggered	Generic High Entropy Secret	02abcda	lib/src/discovery.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}