Frequently Asked Questions: classification, verification and agent safety

The Category

Is REVsign a CDP?

Yes, a CDP for Go-To-Market. A CDP is the platform that unifies your customer data in one place. REVsign unifies that data and also what happens outside (companies, people and public market narratives) in a Unified Signal Layer.

The difference with classic ones is what happens next: they store and segment. REVsign verifies every datum against its source, scores it with fixed rules, proposes what to do and waits for a person’s sign-off before anything goes out to a third party. It does not replace your CRM: it connects to it, or runs without one. The detail is in Signal Architecture.

Commercial Outreach

How does cold outbound work without becoming spam or commercial noise?

In B2B it is called signal-based or intent-based outreach: a first message with no prior consent, but justified by a verifiable fact about the account. Autonomous GTM only prepares outreach when three conditions are met at once:

• The right account. The intent score picks it by sector, size and change history, with fixed rules.
• The person who decides. Their contact data is revealed only once their real function is validated against the purchase, not their declared title.
• The reason. A current fact, with a verbatim quote and a traceable source.

Two safeguards sit on top. A safety gate blocks sending to accounts on the exclusion list and to contacts who received a message in the last 90 days. And a signature gate holds every draft until a person approves it.

The Classification Engine

Why does REVsign ignore traditional corporate titles, and how does it identify the real decision-maker?

A traditional tracker that filters by job-title taxonomy (“VP of Growth”, “Head of Sales”) inherits a problem at the source: a LinkedIn title is a declaration, not a verification. The label can be stale, honorific, or simply not reflect who actually executes inside the organization, and a rigid taxonomy that trusts that text produces systematic false positives.

REVsign evaluates every contact with its own persona classifier, which runs on the smallest model in the Claude family. Instead of comparing the declared title against a list of target job titles, it compares vocabulary and real execution capacity against the target buyer persona. The output is never a boolean: it’s one of three states, clear fit, plausible fit, or rejected.

This is the direct application of the system’s first Founding Mandate: function dictates reality, not the label.

Financial Governance

Why does REVsign reveal contact data last, and how does that protect the budget?

A candidate reaches the classifier with no contact data, no email, no phone. It isn’t a field marked hidden: that data simply isn’t part of the object at that point in the process.

Revealing a contact’s email or phone is a real, billed enrichment call. The system only fires it after the persona classifier has approved the fit (clear or plausible). A rejected contact never triggers that call. The result: enrichment budget gets spent only on contacts that already cleared the bar of being worth a look, not on every row of a raw prospecting list.

Data Infrastructure

How does the Unified Signal Layer work, and how are corporate identities verified?

The Unified Signal Layer is the infrastructure described in Signal Architecture: one source of truth, no per-system duplicate copies. Before a domain enters that layer, it goes through a multi-step verification:

1. Active domain probe. A visit to the site that follows redirects rules out dead or parked domains. A single check isn’t enough: it takes two consecutive confirmations before a domain gets marked dead or parked, so a transient network error never gets penalized.
2. Tax ID (CUIT) validation. The arithmetic that defines the number itself and prefix rules for individuals vs. legal entities validate the format. Cross-referencing against Argentina’s AFIP tax registry via AfipSDK is built but not yet validated with real production credentials, it only goes live once the environment has them configured, and until then the company stays at a “pending” status on that field.
3. Corporate network mapping. Companies sharing a CUIT but with different domains get flagged as merge candidates by brand-name and CUIT match. They’re never auto-merged: they always surface as a signal for human review.

Lines of Work

What lines of work does the engine cover?

Hallucination Prevention

How does REVsign guarantee auditable integrity and keep AI from making up information?

Every analysis that cites a source must carry, for each claim, the exact fragment that backs it and which part of the original text it came from. Before that synthesis reaches any briefing, a mechanical validator checks that the quote is a literal fragment of the original content: the same words, in the same order, with none added or removed. It only ignores differences in spacing, curly quotes and formatting marks that do not change what was quoted. It does not accept a semantic or fuzzy match.

If a single citation fails to verify, the system throws a contract error and discards the entire synthesis. No partial version gets saved, and nothing that passed gets carried forward on its own. This forces the model to act as an extraction engine over raw text, not a free-text generator that merely looks like it’s citing something.

Agent Security

How are autonomous agents kept from operating outside their parameters?

Every agent has, in the code, not in the instructions given to the model, an explicit list of tools it may invoke (for several agents, none at all), a per-call writing cap, and an iteration cap. The model doesn’t “choose not to use” a tool outside that list: it simply doesn’t exist for that invocation, because it’s never described to it.

Each agent’s output is also checked against the exact shape it must have, right at the boundary of the call. Any deviation from the expected shape throws an immediate error that halts execution, with a capped repair-retry budget, never unlimited. The internal team calls this the “digital straitjacket”: constraints written as executable code, not as a suggestion a model could misread or ignore under pressure.

$ curl revsign.os/docs/faq
→ {
  title:    "Frequently Asked Questions: classification, verification and agent safety",
  answers:  "How does REVsign avoid title-based false positives, premature enrichment spend, and agent hallucination?",
  schema:   [FAQPage]
}