Walkthrough
How Piko works, step by step
From a question to a reissued document and everything it touches — what runs today on the reference machine, labelled available, pilot or planned, item by item.
2 min 18 sec
The full loop, ingest to reissue impact, start to finish.
Measured on the reference machine.
The script
Ask, evidence, decision, examination, reissue, outage
This is the same sequence used to demonstrate Piko on the reference machine. Each step says what actually happens.
Ask a real question
“Why did we choose Option B?” goes to the Console. Piko returns a concise answer with its scope and its sources attached, not a paragraph you have to mine for a citation.
AvailableOpen the evidence
Every claim behind that answer carries a quote checked verbatim against its source before it was ever stored. The Console distinguishes an approved position from an assumption still awaiting review — it never presents one as the other.
AvailableSee the decision record
The decision itself is a first-class record resting on approved claims, with an audit trail: what was known, what was approved, and when. Not a memory that leaves with whoever made the call.
AvailableAsk Piko to argue the other side
On request, the model raises the opposing case using only cited evidence, and names the gaps it can’t answer — a structured second opinion instead of a confident monologue. Dispatching a named gap as scheduled, budgeted research is planned.
AvailableReissue a source document
A supplier bulletin, a regulation, or a manual gets replaced. Piko re-anchors the citations that pointed at it and tells you which decisions rested on the passage that changed — ranked by which has a commitment coming due. This is the case no wiki, drive, or chatbot handles, because none of them track the link between a document and the decisions resting on it.
AvailableKeep working through an outage
Local retrieval, citations, the review queue, and at least one approved local model don’t depend on an internet connection or a cloud login. Working locally. Web research is paused.
AvailableMeasured, not estimated
What was actually timed, on the reference machine
Each number below was measured on the reference machine — an Apple M4 Mac mini, 16 GiB — and is not a promise about performance on other hardware.
2 min 18 sec
The full loop — ingest, extract, model review, examination, approval, decision, reissue, impact — start to finish.
Measured on the reference machine.
128 / 128
Jobs submitted and completed over an eight-hour continuous run, zero failures, including a deliberately killed worker that recovered with no work repeated.
Measured on the reference machine.
$0.00
Cloud cost over that run, with the spend ledger checked empty rather than assumed.
Measured on the reference machine.
Not built yet
What this walkthrough leaves out, on purpose
Connecting external AI assistants over MCP, cloud model providers, and paid web search are planned, not available. There is no hosted or multi-company offering — Piko runs on hardware the business owns — and no mobile app or third-party integrations yet. If a step needed one of these to be true, it was left out rather than softened.