From a stand to a card
The flow · version 0.1 · the same picture runs the work and explains it
How a company met at Web Summit becomes a GAMMA-Ray card with FACT-Ray trust on every fact: who does each step, a person, an agent or code, what each step leaves on record, and how far the facts can be trusted after it.
a personan agentcodeπ: how far the facts can be trusted after that step (FACT-Ray)
Trust rises in two ways: more people and agents stand behind a fact (Accountability), and the source moves closer to the company and its customers (Source). Our own reading of a public page, however careful, stays at Source 1. The strongest claim is the company's own, on its own domain, checked by someone who answers for it.
The twelve steps
- 1Meeta personDinis Cruz, or the interview team
Meets the company at its stand, at a talk or in an interview, and takes a photo or a note.
- 2Intakean agentgamma.field@web-summit.dinis
Writes down the stand's own words, exactly, with where and when.
The company said it on its own stand; our record is not public; nobody has checked it.
- 3Identifyan agentgamma.field@web-summit.dinis
Names the company, the product and the part that may be an agent, with its domain.
- 4Is there an agent?an agentgamma.field@web-summit.dinis
Asks whether anything acts on its own. If not, the intake stays and no card is made. That is not a no.
- 5Readan agentgamma.field@web-summit.dinis
Reads the public pages, the documentation, the trust centre, llms.txt and the company's own /.well-known/fact-ray.json.
We found it on a public page anyone can open; nobody else has checked it.
- 6Capturecodetools/capture.mjs
Fetches every source once, hashes it, keeps it in a public vault.
- 7Mapan agentgamma.field@web-summit.dinis, with an assessor and a challenger
Maps each piece of evidence to an indicator, with its source, grade, mode and the exact words. Never assigns a level.
- 8Scorecodebuild/spectrum.mjs, build/factray.mjs, build/graph.mjs
Computes the levels, the trust of each fact, and the card's graph down to the source.
- 9Reviewan agentgamma.review@web-summit.dinis
Two rounds: opens every source again and argues against every high level.
Captured, hashed and checked by another agent.
- 10Sign off and publishan agentgamma.approve@web-summit.dinis
Reads both rounds and signs off. The card is published as beta, with the status Draft.
- 11Talka personthe interview team and Dinis Cruz, with gamma.studio@web-summit.dinis
The interview links to the card. The company is asked to confirm or correct each fact, or to publish its own file; a customer to state how it uses the product.
The company says it on its own domain, with a page to open.
- 12Confirm or attesta personthe company, a customer, Dinis Cruz
The company confirms (Confirmed), a customer goes on record (Attested), the operator signs a scope (A4). Every correction goes back to step 8.
A customer on its own domain, signed by the person who answers for it.
Two loops
- A review finding goes back to the mapper, who answers it in the scan before the next round.
- A correction from the company or a customer goes back to the scorer. Nothing is deleted: the old fact is superseded, and every page that depended on it changes with it.
Where it stands
2 companies met so far: 0 at intake, 0 being drafted, 1 in review, 0 published, 1 with no agent found. A company appears on this site only when its card has passed two rounds of review and a sign-off; until then it is in the repository's data/intake/, and no photo that shows people is kept there.
The flow is data: flow.json. The newsroom of PrompTugal.news reads it to draw the same picture for its own pieces.