Skip to content

design(permissions): the authorization system #50

Open

Description

@PiquelChips

piquel is designing a proper authorization system for Origin. This issue holds that design.

What it has to answer for a public host:

  • Who may read, propose, annotate and land when a policy says nothing.
  • How "everyone" differs between a team's server and a host where anyone can register.
  • How it fits the rule that policy is a target, so permissions stay ordered, reviewed and audited like code.

Plan: sourceorigin-dev/sourceorigin#527, docs/plans/platform/origin.md.

Note

Written by Claude Fable 5.2 in Claude Code (via T3 Code)

Activity

  1. added this to the v0.2 milestone on Nov 13, 2026
  2. added
    questionFurther information is requested
    area/permissionsCapabilities, path rules, credentials and tokens
    on Nov 13, 2026
  3. added theissue type on Nov 13, 2026
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

    area/permissionsCapabilities, path rules, credentials and tokensquestionFurther information is requested

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions