Build console
Behind the scenes: how content flows in, what's covered, what access we still need, and the decisions waiting on Marco.
How content flows into the terminal
From raw manuals to a live alert. Each stage is reviewed by you before anything reaches the team.
Sources
4 manuals + hyperlinked docs
Parse & clean
split, flag conflicts, capture links
Review gate
you: keep / fix / send to Decisions
Structured store
one source of truth
AI feed
same store, as data
Detection → Alert
watches data, emails the manager
Decisions
conflicts → Marco, then publish
↺ Conflicts are quarantined and sent to Decisions. Once Marco rules, that content publishes and can fire alerts.
Sources & access
For each manual: how much is pulled in and cleaned, and exactly which hyperlinked docs we still need. Request access right here.
Decisions for Marco
Where the manuals disagree, the AI can't pick. Marco settles each one; answers save permanently. This list grows as we review more data.
📈 Right now there are 5 open. Expect many more as we go through the manuals together, point by point.
⚠ Couldn't reach the server to load saved answers. You can still type, but check your internet before saving.