Set up
Products
A product is a thing being taken to market, not a company. Give it a name and say where to read about it — its documents and its repositories. Claude and Codex then comb what you gave them, argue with each other about it, and write down what this product is and what it can do. You check their work on Knowledge; nothing they conclude counts until you do.
New product
A slug that already exists updates that product rather than creating a second one — the form is a desired state, not an insert.
Lontra
lontrathe one you are working oncreated 2026-09-28What is read about it
- GitHub repositoryLontratech/landing-lontra· never read
- Uploaded filesLontra_Global_GTM_Report.pdf· read 2026-09-28
Where it lives
Where this product’s work happens. Several of each is normal: Lontra is lontra-fo and lontra-bo. A landing-page repository is also read for how its pages are built, so a new one matches.
Stop building into it
Nothing built there is removed and the record of where it came from stays. Only new work stops going to it.
Onboarding document — save as fixtures/core/lontra.json to keep the record in git
Re-apply it with npm run tenant:onboard. It is the same document this form writes, so the file and the page cannot drift.
{
"slug": "lontra",
"name": "Lontra",
"description": null,
"owners": [],
"config": {},
"credentials": [],
"sources": [
{
"kind": "github",
"name": "Lontratech/landing-lontra",
"config": {
"repository": "Lontratech/landing-lontra"
}
},
{
"kind": "upload",
"name": "Lontra_Global_GTM_Report.pdf",
"config": {}
}
],
"repositories": [
{
"repo": "Lontratech/landing-lontra",
"purpose": "landing-page",
"label": null,
"base_branch": "main",
"subdirectory": "",
"push_policy": "pull-request"
}
],
"capabilities": []
}