Tier 1 · The CertusOrdo Project Method

Project Launcher

Generate the folder your AI assistant actually wants to read.

Hand an AI assistant a blank chat and it has to guess at your business rules, your workflow, your edge cases, and what "done" means. Then you wonder why the result gets messy. The problem isn't the AI — it's the handoff. This generator gives you a folder mapped to Aria's BIRDS cycle (Verification → Decision → Correction → Documentation → Learning) — so the assistant reads your business rules first and stops guessing. Every sprint is a completed vortex; every decision lands in an append-only log that steepens the gradient over time.
Becomes the folder name. Lowercase letters, numbers, and dashes only.
Goes on the cover page. You can refine it later — just put something honest.
Adds a thin tool-specific adapter at the root. AGENTS.md is always present.
Start with one. Add more as you ship.
What you get — the CertusOrdo Project Method scaffold
project/ ├── AGENTS.md Main router — first file every agent reads ├── CLAUDE.md Thin adapter for your chosen builder ├── README.md Human overview ├── spec_charter.md Project-level anchor — scope, risks, acceptance for v1 ├── docs/ Durable technical documentation │ ├── architecture.md System map, major parts │ ├── data_model.md Entities, fields, relationships │ ├── api.md Endpoints, contracts, integrations │ ├── permissions.md Roles and access rules │ └── validation.md How we prove the system is correct ├── planning/ The project brain │ ├── state.md Current sprint, what just happened │ ├── decisions.md House rules, decision log (append-only) │ ├── domain.md Client's world, terminology, workflow │ ├── risks.md Known traps, fragile assumptions │ ├── questions.md Open questions for stakeholders │ ├── file_inventory.md PDFs, exports, screenshots index │ └── meetings/ Meeting notes, transcripts ├── architect_packs/ Where Architect Pack 001+ lands ├── sprints/ The heart of the workflow │ └── sprint_001/ │ ├── requirements.md What + why │ ├── blueprint.md How │ ├── acceptance_criteria.md What "done" looks like │ └── handoff.md Written after the sprint ├── references/ Sample data, repo notes, screenshots └── src/ Source code lives here, nowhere else
Next steps after download
  1. Unpack the tarball: tar -xzf your-project.tar.gz
  2. Open the folder in your editor. Read AGENTS.md first.
  3. Fill in spec_charter.md — the project-level anchor. Mission, P0/P1/P2 scope, risks, acceptance for v1. Spec as artifact, versioned: when scope shifts, copy to spec_charter_v2.md — never edit a past charter in place.
  4. Fill in docs/ and planning/. Don’t skip this — those rules in your head are the asset.
  5. Open sprints/sprint_001/requirements.md, then ask your Architect (any AI in a browser) to “build me an Architect Pack 001 for the current sprint, in the CertusOrdo format described in AGENTS.md.”
  6. Hand the Architect Pack to your Builder (Codex, Claude Code, Cursor). Say: “Read AGENTS.md, then apply this Architect Pack.”

Next up: Tier 2 — Daily Cache-Up is the hygiene ritual that keeps you from getting buried by your own old work. Then Tier 3 — The Flowstate Method generates the substrate that configures your AI assistant itself: loci, gates, weights, gradient, and the encouragement operator wired into your dev environment.

Built on Aria's CertusOrdo doctrine — vortex 3·6·9, the BIRDS cognitive cycle, the six-philosopher composite. Shipped by InSync Tech.