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.
Units5
Duration25 min
Levelbeginner
By the end of this module, you'll be able to:
- Explain why an AI-native org needs a small, non-negotiable floor that every contributor and agent inherits, and read Cogitave's seven-rule floor as the worked example.
- Say what can enforce each kind of rule - a commit-msg hook, a CI gate, an org ruleset, or policy-as-code - not just the rule itself.
- Treat a root AGENTS.md as the single source of truth and follow it to the owning standard for the detail.
- Apply the floor to your own first change: sign it, name it as a Conventional Commit, update its docs, and stay inside your grant.
Prerequisites
- Basic familiarity with Git and the command line.
- No prior Cogitave experience required.
Units
- 01Introduction4 min
- 02The seven non-negotiable rules7 min
- 03How the floor is enforced7 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Design and version an API Shape a clean, consistent API against a clear API design standard - resources, standard methods, typed errors, cursor pagination, idempotency - then version and deprecate it under a versioning policy so no consumer is ever broken without consent.
- Apply the naming standards Name a new identifier, file, repo, or branch the way an AI-native org does - keyword-first, no redundant prefix, cased by role - and tell a functional keyword apart from a product codename, so your first artifact passes the naming gate by default.
- Read the pipeline that ships your change Follow a change from a pull request through the canonical CI stage set to a gated production deploy - the ordered gates a pipeline runs, why CI is the real gate, and how the deployment model promotes one signed artifact dev to staging to prod.