A specification defines the work. Agora governs its execution.
Roles, permissions, states, gates, evidence, handoffs and approvals that survive the session and remain inspectable in Markdown and Git.
The problem left after the prompt
A result is not traceability.
A pull request may contain code, tests and a convincing explanation. It still does not prove who executed, what decisions were delegated, what evidence a person reviewed, or who had authority to accept.
What it could decide
What was produced and verified
Who accepted the result
How it works
Process becomes verifiable configuration.
Agora does not replace Jira, GitHub, CI/CD or the agent runtime. It defines and records the contract connecting those systems.
- 01
Choose the method
Spec-driven, Scrum, Kanban or a custom Method Pack.
- 02
Assign actors to roles
Humans, agents, services or swarms with explicit capabilities.
- 03
Execute within the lifecycle
Every transition is checked against permissions, gates and required evidence.
- 04
Keep the record
Decisions, sessions, handoffs, tool runs and approvals remain in .agora/ and Git.
Agora ecosystem
Three projects. One source of rules.
Governance and durable state
Application services, CLI, Method Packs, Tool Packs, gates, evidence and persistence.
GitHub ↗Local visual control plane
Browse projects, work, lifecycle, activity, evidence, traceability and gates.
GitHub ↗Executable demonstration
Game, LLM agents, local providers, observability and governed development records.
GitHub ↗Product status
Ready for evaluation and controlled pilots.
Agora is alpha software. CLI and Markdown contracts may evolve before 1.0; every organization must review permissions, Method Packs, adapters and isolation.