Ask in your own words, or ask for something to be run.
Or ask for something to be run. A request comes back as a proposal — the workflow, and the exact input it would receive — and nothing is queued until you approve it.
Counting…
Checking what rests on what…
Nothing is in market for Lontra.
No page has ever been published, so nothing has been tested on anybody. Everything upstream — the knowledge, the research, the profiles — is worth exactly what it produces at this end.
An artifact whose inputs have moved since it was produced. Checked against what each kind declares it rests on — never assumed.
Cannot be determined
Checked, and current
Derived from what is missing: a stage is next when everything it rests on exists and its own output does not. Any of them can be asked for in the chat above.
npm run understand -- --tenant <slug>npm run discover:reddit -- --tenant <slug>npm run topics -- --tenant <slug>npm run capabilities:propose -- --tenant <slug>The detail behind the figures at the top of the page — one read, so the two cannot disagree. Every count links to the surface that owns it.
1 document · 0 chunks, 0 embedded
0 capabilities in the register — what a claim may rest on.
No market source has been read for this product yet.
npm run market:context -- --tenant <slug>npm run probe -- --tenant <slug> --source <source> --ask "…"Nothing is reachable by anyone outside this application.
No campaign ties an ICP, a page version and a channel together yet.
npm run experiment -- --tenant lontraDocuments
1
2 sources · 0 of 0 chunks embedded
Awaiting validation
0
9 validated
Capabilities
0
confirmed — what a published claim may rest on
Signals
0
no market source has been read yet
Live pages
0
nothing is reachable from outside this application
Running now
0
the queue is empty
Counted from rows. What a published page did — visits, click-throughs, leads — is on Attribution and Results, where a rate carries its interval; nothing appears here that was not measured.