Inherit the project baseline
How a new repository is born on the paved road with its whole ruleset already inherited, how to tell always-on standards from the ones a product type pulls in, and how to find an existing pattern before writing anything new.
Units5
Duration23 min
Levelbeginner
By the end of this module, you'll be able to:
- Explain how a new repository inherits its complete ruleset automatically - the floor, the standards, the scaffold, the lifecycle, and the identity - instead of re-deciding the rules.
- Scaffold a repo from a base template plus its per-type template so the baseline is baked in from birth.
- Distinguish always-on standards from the conditional standards a product type additionally pulls in.
- Apply reuse-first / discover-before-generate: query the patterns catalog and start from a named artifact before writing new code.
- State honestly what is enforced today versus what turns on at cutover.
Prerequisites
- Familiarity with the org's non-negotiable rules (the AGENTS floor).
- Basic familiarity with Git and the command line.
Units
- 01Introduction4 min
- 02What the baseline gives you6 min
- 03Reuse first - discover before you build6 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Open your first pull request Apply an AI-native org's floor, its inherited baseline, and the request lifecycle in one hands-on contribution - a signed, Conventional-Commit, docs-complete pull request that passes the gates and stops for human review.
- Work the request lifecycle Move a change through the seven-stage request lifecycle, understand why the write tools only propose, and read the Definition of Done that decides when a request is actually done rather than merely worked on.
- Apply a non-negotiable floor An AI-native org runs on a small floor every human and agent obeys. Study Cogitave's floor - its seven non-negotiable rules and what enforces each, from a commit-msg hook to policy-as-code - then apply a floor like it to your own first change.