Shared public development culture, contributor intake, education, and maintenance workflows for the repo family.
@dev/intake and pathway structure- automation support
- courses and contributor learning
- shared maintenance notes and scripts
- canonical runtime ownership
- provider transport ownership
- private product ownership
@dev/requests/@dev/submissions/@dev/pathways/@dev/notes/automation/courses/docs/scripts/
Use this repo to coordinate work across the family without turning it into a monolith.
The active v2.3 lane now uses a workflow-backed schedule model where
scheduled work refreshes evidence and manual work owns final binder lifecycle
transitions.
docs/family-workflow.mddocs/repo-sync-policy.mddocs/repo-family-map.mddocs/conformance-sweep.mddocs/public-structure-sweep.md@dev/notes/roadmap/v2-family-roadmap.mddocs/development-roadmap.mddocs/roadmap-workflow.mddocs/workflow-schedule-operations.mddocs/release-surfaces.mddocs/release-matrix.mddocs/release-backlog.mddocs/versioning-policy.mddocs/activation.mdautomation/.github/workflows/
uDOS-dev defines development practice, not runtime semantics.
The v2 repo activation path is documented in docs/activation.md.
Run the current repo validation entrypoint with:
scripts/run-dev-checks.sh