Onboard theam/facility as the governed reference project (dogfood)
Open
Nobody has claimed this yet.
priority:urgent
type:feature
- Dominant language
- TypeScript
- Stars
- 71
- Forks
- 64
- Avg merge
- 15h 38m
- Merged PRs (30d)
- 66
Description
Make theam/facility itself the reference project governed by a persistent Facility instance — the cleanest dogfood loop there is: every improvement to the platform is also a test of the platform.
Scope
- Connect the repository to a persistent instance and enable all lanes: architect, builder, review, security, doctor, learning.
- Drive at least one real backlog item through the full governed loop: issue → architect plan → human approval → builder PR → review → human merge → outcome ingested.
- Capture friction and breakage as issues here — that feed is the point of dogfooding.
Acceptance
- Facility's own board shows a governed run end to end on a real change that merged to
main. - The learning agent has produced at least one proposal from a run on this repository.
- Onboarding friction is documented as issues.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the repository connection and persistent Facility instance setup, then trace how the architect, builder, review, security, doctor, and learning lanes appear on the Facility board. Done means a real change reaches main through the governed loop, produces a learning proposal, and records onboarding friction as issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai-infra-agents, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100