Authority agent guide

Mission

Authority is the platform OIDC/OAuth2 control plane that mints short-lived, sender-constrained operational tokens (OpToks) for every StellaOps service and tool.

Key docs

• Module README
• Architecture
• Implementation plan
• Task board
• Observability runbook and Grafana JSON (offline import)
• Identity-provider bundle runbook

How to get started

1. Open sprint file /docs/implplan/SPRINT_*.md and locate the stories referencing this module.
2. Review ./TASKS.md for local follow-ups and confirm status transitions (TODO → DOING → DONE/BLOCKED).
3. Read the architecture and README for domain context before editing code or docs.
4. Coordinate cross-module changes in the main /AGENTS.md description and through the sprint plan.

Guardrails

• Honour the Aggregation-Only Contract where applicable (see …/…/aoc/aggregation-only-contract.md).
• Preserve determinism: sort outputs, normalise timestamps (UTC ISO-8601), and avoid machine-specific artefacts.
• Keep Offline Kit parity in mind—document air-gapped workflows for any new feature.
• Keep identity-provider configuration and executable bundles separate: configuration is global Authority state; LDAP/OIDC/SAML code must arrive through an admitted, read-only signed bundle and requires an Authority restart to join DI.
• Keep all tracked Authority provider YAML in devops/etc/authority/plugins/; plugin overlays inherit /app/etc/authority/plugins and only change bundle scan roots.
• Update runbooks/observability assets when operational characteristics change.

Required Reading

• docs/modules/authority/README.md
• docs/modules/authority/architecture.md
• docs/modules/authority/implementation_plan.md
• docs/modules/platform/architecture-overview.md

Working Agreement

• 1. Update task status to DOING/DONE in both correspoding sprint file /docs/implplan/SPRINT_*.md and the local TASKS.md when you start or finish work.
• 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
• 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
• 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
• 5. Revert to TODO if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.