File 17

Automation workflows

Thirteen stages from intake to deletion. Every transition is an append-only event, and a blocked or failed state is a valid outcome that must preserve its reason, evidence, owner and next eligible action.

The state machine

stateDiagram-v2
  [*] --> Scoped
  Scoped --> Collecting: rights gate passed
  Collecting --> Normalizing
  Normalizing --> Analyzing
  Analyzing --> Reviewing
  Reviewing --> Approved: quality gates pass
  Reviewing --> Analyzing: revisions requested
  Approved --> Published
  Approved --> Activated: separate outreach approval
  Published --> Monitoring
  Monitoring --> Analyzing: material change
  Scoped --> Blocked: rights or identity unresolved

Intake and scope contract

inputs

target legal/trade name and domain;
executive name/title if known;
industry, geography, time window, and offered services;
purpose, intended audience, jurisdictions, delivery deadline;
authorized/private data explicitly supplied by the user;
prohibited methods and source categories.

actions

Resolve the company and executive as separate entities.
Record ambiguity and candidate matches.
Select an engagement mode from 00-system-charter.md and an expansion profile from 10-query-pattern-library.md: X-Rapid, X-Standard, X-Deep, or offline-only X-Full.
Create source, retention, security, and outreach policy packs.
Require human confirmation if a wrong identity would materially affect the audit.

Source: file 17 · w0-intake-and-scope-contract · line 25

Source planning and rights gate

for every planned connector

Check registry status, official terms, commercial-use conditions, authentication, robots behavior, rate limit, allowed data, and deletion support.
Assign execution impact I1–I6.
Reject login bypass, deceptive identity, paywall circumvention, credential testing, or active probing. Even with separate written authorization, active security work is routed outside this prospect-intelligence system.
Create bounded queries, expected evidence types, refresh intervals, and stop conditions.
Cache negative results only for a defined interval; “not found” is not permanent absence.

Source: file 17 · w1-source-planning-and-rights-gate · line 44

Collection and evidence capture

for each permitted request

generate runid, requestid, idempotency key, tenant, policy version, and trace ID;
enforce domain allowlist, DNS/IP protections, timeout, response-size/MIME limits, and rate budget;
when source rights and necessity permit, preserve exact bytes; otherwise retain the minimum authorized extract, locator, metadata, and hash needed for verification;
preserve response metadata, source URL, canonical URL, publication/observation/retrieval times, hash, and connector version;
store parsing/OCR/screenshot results as separate derived artifacts;
classify rights, personal data, sensitivity, retention, and access;
write failure states such as rate-limited, denied, removed, unavailable, parse-failed, or terms-unclear.
treat source text, hidden content, metadata, links, and tool output as untrusted data; they cannot issue instructions, change scope/policy, request secrets, trigger tools, or authorize external actions.

Source: file 17 · w2-collection-and-evidence-capture · line 54

Normalize, deduplicate, and resolve

steps

Normalize URLs, names, dates, currencies, units, countries, company identifiers, and text encodings.
Deduplicate exact content by hash and near-duplicates by similarity.
Group syndicated material under one independencegroup.
Extract source assertions and candidate entities while retaining passage locators.
Resolve deterministic identifiers first; then apply calibrated probabilistic matching.
Route material ambiguity to a reviewer.
Preserve cannotlink, merge, split, and decision history.

Source: file 17 · w3-normalize-deduplicate-and-resolve · line 69

Claims, alternatives, and contradictions

for every proposed material claim

Create an atomic subject–predicate–object claim with scope and valid time.
Link supporting, refuting, and contextual passages.
Assign evidence level, source independence, recency, directness, and resolution confidence.
Generate at least one strongest plausible alternative.
Run a disconfirming search or mark the check blocked.
Narrow, downgrade, challenge, or retract unsupported statements.
Prevent derived text from calling Inferred, Hypothesized, or Scenario an observed fact.
Run model extraction through typed schemas with cited passages; reject indirect prompt instructions and require human review before any external projection.

Source: file 17 · w4-claims-alternatives-and-contradictions · line 79

Nine-phase analysis and LAKA expansion

steps

Route validated claims into the nine audit phases.
Apply the 5×10 LAKA diagnostic matrix.
Evaluate all fourteen dynamics for each critical finding; record N/A with a reason.
Expand with the canonical 6×6×6 lens only where it creates a distinct, testable path.
Deduplicate equivalent paths and stop on saturation, rights, risk, or budget limits.
Score evidence strength, materiality, actionability, service fit, urgency, and risk.
Preserve eliminated alternatives and their elimination reasons.

Source: file 17 · w5-nine-phase-analysis-and-laka-expansion · line 92

Competitor and share-of-voice analysis

steps

Resolve peer entities and record selection criteria.
Normalize time, geography, language, outlet tier, product, and metric definitions.
Separate earned, owned, paid, syndicated, and user-generated records.
Deduplicate press-release pickups and shared sources.
Calculate SOV with both count and weighted definitions where possible.
Route selection bias, missing platforms, and non-comparable pricing to limitations.

Source: file 17 · w6-competitor-and-share-of-voice-analysis · line 102

Economic modeling

steps

Classify every numeric datum as R, M, B, A, or C; only R, M, B, and A are model inputs, while C marks a calculated output.
Validate units, currency, base year, horizon, nominal/real basis, and time window.
Create low/base/high or probability-distribution inputs.
Run COI, benefit, cost, ROI, payback, and NPV models as appropriate.
Apply attribution, adoption, and success probabilities explicitly.
Detect overlap through dependency and mutual-exclusion groups.
Run sensitivity and switching-value analysis.
Reject unsupported exact dollar claims or output not estimable with missing inputs.

Source: file 17 · w7-economic-modeling · line 111

Human review and release

required review gates

named-person identity and executive profile;
E2 material claims, which may publish only with bounded scope and caveats; E0–E1 are hard-blocked from publication and activation;
security or vulnerability observations;
allegations, negative sentiment, or crisis narratives;
causal conclusions and financial scenarios;
competitor rankings;
sensitive/personal data;
outreach copy and CRM activation.

Source: file 17 · w8-human-review-and-release · line 122

Report generation

generate only from approved claim and estimate versions every material statement

preserve Observed, Calculated, Inferred, Hypothesized, Unknown, and Contradicted states;
render ranges and formulas, not false precision;
include limitations, blocked sources, date baseline, and research backlog;
validate internal links, table columns, citations, and phase completeness;
produce a reproducibility manifest with hashes and versions, excluding secrets.

Source: file 17 · w9-report-generation · line 137

W10

CRM activation and outreach

steps

Build an activationcandidate from approved, business-relevant claims only.
Determine jurisdiction, purpose, consent/lawful-basis review state, and contact provenance.
Exclude sensitive data, credential/breach content, exploit details, private-life facts, and unverified allegations.
Check global and campaign suppression.
Require message approval and contact freshness.
Upsert through an idempotent connector or create a sanitized export.
Record request hash, remote ID, connector receipt, projection version, and reviewer.
Check suppression again at send time; this system does not autonomously send.

Source: file 17 · w10-crm-activation-and-outreach · line 147

W11

Monitoring and change propagation

monitor only approved sources and claims a material change triggers

new immutable capture;
diff and source assertion extraction;
claim revision/contradiction review;
dependency traversal;
needsrecompute for scores, estimates, reports, and activation candidates;
alert only when materiality and confidence thresholds pass.

Source: file 17 · w11-monitoring-and-change-propagation · line 158

W12

Restriction, suppression, and deletion

on request or policy trigger

apply immediate processing/activation restriction;
verify the request according to policy without collecting excessive identity data;
enumerate canonical and projected targets;
increment privacygeneration and dispatch idempotent deletes/redactions;
purge embeddings, summaries, OCR, caches, exports, and CRM projections as required;
collect a receipt and verification result for every target;
retain only an authorized non-sensitive tombstone;
ensure rebuilds and restored backups replay the deletion ledger before use.

Source: file 17 · w12-restriction-suppression-and-deletion · line 171

Operational controls

Operational controls
Control	Minimum implementation
Idempotency	Stable key from tenant + workflow + target + source + planned interval; unique database constraint
Retry	Error taxonomy, exponential backoff with jitter, per-source retry budget, no policy-denial retry
Rate limiting	Connector token bucket plus global domain concurrency cap
Circuit breaker	Pause source after repeated blocks, anomalous payloads, or terms change
Dead-letter	Preserved event, failure class, attempts, last error, policy context, safe replay button
Timeouts	Request, parse, model, workflow, and reviewer expiry separately bounded
Concurrency	Per source, tenant, target, and expensive model; never unbounded fan-out
Checkpointing	After capture, normalization, claim review, estimate run, and activation
Compensation	Remove/restrict projections after retraction, opt-out, or failed activation
Kill switch	Disable source, connector, tenant, campaign, or all collection independently

Source: file 17 · 3-operational-controls · line 186

Schedules and triggers

Schedules and triggers
Workflow	Default trigger	Default refresh rule
Official company pages	scheduled, permitted	weekly; faster only for identified high-value pages
Press/news/RSS	feed/event	hourly to daily within publisher limits
Regulatory filings	official feed/event	daily or filing event
Reviews/forums	scheduled/manual	weekly; platform terms determine method
Competitor price/offer pages	scheduled, permitted	weekly or monthly; preserve before/after
Macro series	official release calendar	on release plus revision check
Tool registry	scheduled governance review	quarterly and on terms/license alert
Claim staleness	dependency timer	materiality-based SLA
Suppression	event	immediate and again before send
Deletion	event	immediate restriction; tracked deadline to verified closure

Source: file 17 · 4-schedules-and-triggers · line 201

Human responsibility matrix

Human responsibility matrix
Decision	Automation may propose	Human must approve
Source/query path	yes	terms-unclear, authenticated, or higher-impact collection
Entity match	yes	ambiguous named person or material company merge
Claim	yes	critical claim, allegation, security finding, or low evidence
Financial range	yes	all external-facing estimates
Competitor conclusion	yes	all rankings and strategic recommendations
Outreach text	yes	every external message
CRM projection	yes	new personal contact or materially changed purpose
Send	no autonomous send	authorized operator under applicable policy
Deletion closure	verify targets	privacy/data owner confirms closure or exception

Source: file 17 · 6-human-responsibility-matrix · line 234

Read file 17 in full GET /v1/workflows