Skip to content

Diff: architecture/verification-surveyor.es

From 2e843fb to 2e843fb

+0 / −0 lines
BeforeAfter
--- ---
schema: foundry-doc-v1 schema: foundry-doc-v1
title: "Verification Surveyor" title: "Verification Surveyor"
slug: verification-surveyor slug: verification-surveyor
category: architecture category: architecture
type: topic type: topic
quality: stub quality: stub
short_description: "The Verification Surveyor is the human-in-the-loop component of service-people that presents extracted identity fragments to an operator for manual verification before they are permanently committed to the verified ledger." short_description: "The Verification Surveyor is the human-in-the-loop component of service-people that presents extracted identity fragments to an operator for manual verification before they are permanently committed to the verified ledger."
status: active status: active
bcsc_class: public-disclosure-safe bcsc_class: public-disclosure-safe
last_edited: 2026-04-30 last_edited: 2026-04-30
editor: pointsav-engineering editor: pointsav-engineering
cites: [] cites: []
paired_with: verification-surveyor.es.md paired_with: verification-surveyor.es.md
--- ---
> The Verification Surveyor is the architectural checkpoint in service-people that prevents automated extraction errors from compounding by requiring a human operator to confirm each identity fragment against an off-network source before it is committed to the verified ledger. > The Verification Surveyor is the architectural checkpoint in service-people that prevents automated extraction errors from compounding by requiring a human operator to confirm each identity fragment against an off-network source before it is committed to the verified ledger.
Unsupervised extraction algorithms accumulate errors. A fully Unsupervised extraction algorithms accumulate errors. A fully
automated ingestion pipeline processing large volumes of email automated ingestion pipeline processing large volumes of email
will inevitably produce false positives — an "Unsubscribe" link will inevitably produce false positives — an "Unsubscribe" link
parsed as a person's name, a role title extracted from a footer parsed as a person's name, a role title extracted from a footer
rather than a bio. The **Verification Surveyor** is the deliberate rather than a bio. The **Verification Surveyor** is the deliberate
architectural bottleneck that forces all extracted identity architectural bottleneck that forces all extracted identity
fragments through a human cognitive filter before they are fragments through a human cognitive filter before they are
permanently written into the verified ledger. The design accepts permanently written into the verified ledger. The design accepts
the throughput cost in exchange for high-fidelity, long-term the throughput cost in exchange for high-fidelity, long-term
institutional data. institutional data.
## Human-in-the-loop philosophy ## Human-in-the-loop philosophy
Every identity fragment extracted by `service-people` is held as Every identity fragment extracted by `service-people` is held as
unverified until an operator confirms it. The Surveyor presents the unverified until an operator confirms it. The Surveyor presents the
fragment — the extracted text, the inferred entity type, the source fragment — the extracted text, the inferred entity type, the source
context — to the operator. The operator then looks up the individual context — to the operator. The operator then looks up the individual
using their own personal browser and their own personal account on using their own personal browser and their own personal account on
an external directory (such as LinkedIn), confirms the entity, and an external directory (such as LinkedIn), confirms the entity, and
pastes the verified URL back into the terminal. The platform never pastes the verified URL back into the terminal. The platform never
initiates the external lookup itself. initiates the external lookup itself.
This design is deliberate. API-based lookups against external This design is deliberate. API-based lookups against external
directories would require persistent foreign tokens, incur directories would require persistent foreign tokens, incur
per-query costs, and expose the platform to rate-limiting or per-query costs, and expose the platform to rate-limiting or
IP-ban risk. The air-gapped approach avoids all three. IP-ban risk. The air-gapped approach avoids all three.
## Daily throughput limit ## Daily throughput limit
The Surveyor enforces a hard limit of ten verifications per The Surveyor enforces a hard limit of ten verifications per
operator per day. The limit is not a capacity constraint; it is a operator per day. The limit is not a capacity constraint; it is a
quality control mechanism. High-volume data entry at speed quality control mechanism. High-volume data entry at speed
produces habitual approvals rather than genuine verification. Ten produces habitual approvals rather than genuine verification. Ten
careful verifications per day produce roughly 3,650 confirmed careful verifications per day produce roughly 3,650 confirmed
institutional relationships per year with negligible error rate. institutional relationships per year with negligible error rate.
The scarcity is structural: it transforms what would otherwise be The scarcity is structural: it transforms what would otherwise be
a mechanical clearing task into a deliberate, high-attention a mechanical clearing task into a deliberate, high-attention
operational step. operational step.
## See Also ## See Also
- [[ontological-governance|Ontological Governance]] - [[ontological-governance|Ontological Governance]]
- [[message-courier|Message Courier Service]] - [[message-courier|Message Courier Service]]
- [[sovereign-telemetry|Zero-State Telemetry Architecture]] - [[sovereign-telemetry|Zero-State Telemetry Architecture]]
- [[moonshot-initiatives|Moonshot Initiatives]] - [[moonshot-initiatives|Moonshot Initiatives]]
## References ## References