Skip to content

allowed_signers per namespace; remove a stale file #150

Closed as not planned
Closed as not planned

Description

@Hafeok

Issue 7 of ledger/prd/namespace-independence-prd.md §6, opened on the principal's instruction (session ledger/sessions/2026-10-namespace-layout-authority.md).

Cites. PRD §3.4 (allowed_signers).

Size. S. Depends on. Issues 1 and 6.

Appendix C note. Yes.

Rulings carried. 47.

What it builds. One derived file per namespace, ns/<ns>/allowed_signers, holding today's lines for that namespace with valid-before taken from closes in that namespace only. [SIGNERS] compares each namespace's committed file with that namespace's trusted bindings. A namespace that binds nothing has no file, and signers::write removes a stale one (N10). Protocol: LP-4.10, LP-4.32, LP-4.33 per namespace; Appendix B row; Appendix C note.

Acceptance criteria. §3.4: the derived file is per namespace, a close in another namespace does not reach it, a stale file is removed.

Activity

  1. Hafeok commented on Nov 3, 2026

    @Hafeok
    CollaboratorAuthor

    Closed as not carried under D1.24`` and the definition's chapter 8:``` the Rust tool is frozen at rust-final and its tree left `main` in #166 (`53bd547`). This concerns the Rust ledger (its keys, namespaces or authority), which is Writ's authority graph now. The rewrite holds no key and no grant, and `writ import` reads `.decisions/` once, at the tag. Disposition approved on #165.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Effort

    None yet

    Progress

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions