Skip to main content

​
Send new evidence through the same door

Use this milestone to mark that the operator understands the ongoing rule: any new claim discovered after the entity is live goes back through Admin Verify. Not into the entity as truth. Not into activation lanes. Not into reports. Back through the same verification door that inked the original foundation.View in app: open the entity and use its Admin Verify surface — see Admin Verify for the full workflow, keyboard shortcuts, and how the accept / reject / skip queue works. veracity.super-intelligent.ai/entities — sign-in required.When you’d use it:
  • Any time a re-harvest, a new manual claim, or a fresh scan turns up evidence the entity did not have before.
  • Whenever a client sends over a new detail (new address, new phone, new legal name, a schema update on their site) after the entity is live.
  • On an ongoing basis — this is an infinite checklist step, not a one-time acknowledgement.

​
What this milestone is really saying

  • The verification door is the only door. The foundation was inked by walking each claim through Admin Verify. New evidence discovered later has to walk the same path. There is no shortcut for post-go-live claims; the trust properties of the entity only hold if the door stays the door.
  • “Live” does not mean “closed for evidence.” The entity’s state after Core Truth Inked is ready to activate, not sealed. New evidence keeps arriving — from re-harvests, from clients, from routine drift monitoring, from the app itself as providers catch up. All of it queues at Admin Verify.
  • This is the checklist item that stays open. Most lifecycle steps are done once and left. This one is marked as ongoing on purpose — it’s the habit, not the task.

​
What you can do here

  • Open the entity’s Admin Verify surface whenever new claims exist to work. Full behaviour, filters, keyboard shortcuts, and traps are on the Admin Verify page — don’t duplicate that here.
  • Make it part of the monitoring rhythm. Pair this with Monitoring Active and Identity Drift Monitored — those two watch for new evidence appearing; this one is the rule for what to do when it does.

​
What it does not do

  • It does not automatically route anything. New claims don’t get magically funnelled — an operator has to open Admin Verify and work the queue.
  • It does not have its own workspace. The entire behaviour lives on Admin Verify.
Status: Verified · Layer: 1 (ongoing monitoring) — habit indicator, type: 'infinite'; all mechanics live on /lifecycle/admin-verify.