0. Do these in order before Angelica leaves
This is the dependency-ordered autonomy gate. Items 1–7 are mandatory. If any mandatory item fails, the fleet remains local/staging-only and does not compensate by widening permissions or spending.
Fable/Claude 10X correction adopted
Build depth in an evidence-grade domain graph before breadth in a commodity directory. The next product gate is 2,000–5,000 high-value domain organizations with dense relationships, evidence and freshness. The contracts still scale toward 30,000–50,000, but we do not buy generic scale or claim workforce completeness before measured value and rights support it.
Official and company-published facts are labelled OFFICIAL_EVIDENCE. Licensed people-data results are PROVIDER_ATTRIBUTED. Unresolved matches remain UNRESOLVED_CANDIDATE. No vendor record is laundered into first-party evidence.
Unattended operating boundary
During Angelica’s absence, AI TIDES works only in tides-dev, on feature branches and staging/private proof. It cannot approve its own PR, merge to main, deploy production, activate outreach, move funds, connect wallets, or weaken safety/cost controls. Jason can commit the repository HALT control from a phone to stop new jobs.
- Vault and recovery. Confirm the company vault, named owners, billing contacts, MFA, root recovery, incident phone numbers, and a second human who can disable access. Record secret paths, never secret values.
- One isolated development account. Create or confirm AWS Organization plus one member account named
tides-dev. Do not spend tomorrow building dev/stage/prod organizations; blast-radius isolation and durable access come first. - Hard cost stops before compute. Create an AWS Budget Action that attaches a deny policy at the approved ceiling; set low EC2/Batch/Fargate vCPU and concurrency quotas; prohibit NAT Gateway and always-on workers; enable anomaly, security and billing alerts. AWS Budgets alone is not a hard cap.
- Scoped machine identity. Create a GitHub OIDC role limited to
tidesmarket/tides-product, approved feature branches,tides-dev, named resources and Terraform state. No long-lived AWS key in GitHub, chat or a laptop. - Minimal development data plane. Provision private/versioned
tides-mi-raw-devwith Object Lock, derived storage, PostgreSQL dev with PITR, SQS plus DLQ, ECR, Secrets Manager, CloudWatch/CloudTrail and a backup vault. Do not create OpenSearch, Kafka, Kubernetes, multi-region, or always-on browser fleets. - Protect release truth. Protect
main; require passing checks and independent review; disable force push and agent self-approval. Confirm Git-driven production remains unchanged while unattended work accumulates as reviewable PRs. - Prove every kill switch. Run OIDC identity, object write/read/version/replay, DB migration/query/PITR, queue→DLQ, one bounded container job, alarm delivery, Budget Action deny, repository
HALT, and credential-disable drills. Save a secret-free receipt. - Create capped API projects. Company-own OpenAI, Anthropic, X Developer, Google/YouTube and one search API project. Use real provider hard caps where supported; otherwise use quotas, low prepaid credits and application-side circuit breakers.
- Open calibration accounts, not overlapping contracts. Enable bounded PDL and Apollo trials on the same cohort, plus only the source/provider accounts required for SEC, GLEIF, Companies House, GitHub, YouTube and permitted feeds. Defer Enterprise X, OpenSearch and large data licenses.
- Publish the handoff. Record account/project IDs, human owner, role ARN, resource names, scopes, plan/limits, billing owner, secret paths, verification results, recovery path, rotation date and escalation contacts. Jason receives only decisions and receipts, not credentials.
HALT test—not the estimate—are the acceptance proof.1. Launch definition
Monday launch means a controlled market-intelligence ingestion and monitoring beta, not outreach, an unbounded global scrape, or a claim that the full universe is complete. The launch is ready when a bounded official/public source set can be fetched remotely or locally under one contract, archived with replayable request/response evidence, parsed into canonical entities and relationships, deduplicated, ranked, connected to permitted feeds, monitored for changes, searched, reviewed, and measured for freshness, coverage, errors, throughput, and cost.
Already complete
50-account workbench; 50/50 researched; 46 QA accepted; four false positives rejected; source provenance; fail-closed defect audit; global architecture plan; Git/Vercel publishing.
Monday beta
Source registry and rights state; immutable raw archive; full HTTP sidecars; parser/schema versions; canonical entity and relationship graph; deterministic dedupe plus merge review; ranking model; feed discovery; change events; searchable monitored views; freshness/coverage/error dashboard; measured calibration run.
Post-beta scale
First reach 2,000–5,000 high-value domain organizations with dense evidence and monitoring. Expand toward 30,000–50,000 only after correctness, rights, yield, freshness, demand and unit economics pass.
Fable/Claude and GitHub reuse verdict
Claude Opus 5 completed the requested adversarial Fable role and identified the missing cost and autonomy controls. Adopt only narrow permissive components now: httpx, tenacity, complete JSON fetch sidecars, and conditional warcio. Study Scrapy politeness patterns; defer dlt and Splink to measured triggers; reject OpenSearch, DataHub, Dagster, Common Crawl, Crawlee, Twenty, and NocoDB for v1. Keep production frozen while the reviewer is away.
2. Critical path and owners
| Owner | Deliverable | Hard evidence | Deadline |
|---|---|---|---|
| Angelica | Provision/authorize accounts, billing, domains, roles, vendors, and the credential handoff. | Account IDs, role ARNs, approved secret names, provider workspaces, DNS record receipt—never raw secrets. | Sunday 1:00 PM MDT |
| AI TIDES / engineering | Infrastructure as code, schemas, queues, workers, source catalog, API, admin search, tests, and deployment. | Git SHA, plan/apply logs, seeded-defect pass, staging URL, production receipt. | Monday morning |
| Jason | Named-owner decisions: G0-04 research acceptance, provider/claims boundaries, launch/no-launch. | Dated acceptance receipt with explicit scope. | Before Monday activation |
| Fable/Claude | Red-team architecture, repo quality, source truth, cost/runaway, recovery, and displacement risk. | Structured verdict; access gaps and rejected assumptions visible. | As soon as UI access returns |
3. Angelica’s account and access checklist
Create named human access and separate machine roles. Never issue a shared root login or send long-lived keys in chat.
Cloud ownership and billing
Named access and secrets
4. AWS scale path Angelica should prepare—not block Monday on
The contracts must scale, but current volume fits one process and PostgreSQL. Establish ownership, billing, MFA, and vault access now. Provision queues, Batch, Fargate, OpenSearch, and multi-account production infrastructure only when measured workload triggers require them.
Storage and archive
Database and search
Workers and queues
Observability and recovery
5. Data, enrichment, and verification providers
Angelica should create company-owned workspaces, accept terms using the correct legal entity, enable billing, and store API credentials in the vault/Secrets Manager. Engineering will benchmark providers on the same 250-organization calibration.
| Provider | Angelica action | Use | Acceptance evidence |
|---|---|---|---|
| Apollo | Create/upgrade workspace; request API access and sufficient export/enrichment capacity; invite named operators. | Organization/person enrichment, titles, emails, phones, social URLs. | Workspace ID, plan/API entitlements, permitted-use notes, secret path. |
| People Data Labs | Create production account, enable company/person APIs and bulk enrichment, document license/retention limits. | Independent enrichment coverage and conflict comparison. | Account/project ID, rate limits, DPA/terms receipt, secret path. |
| Hunter or ZeroBounce | Choose at least one independent verifier; enable API and adequate credits. | Email verification, confidence, disposable/catch-all/risk status. | API enabled, test request succeeds, secret path. |
| Browserless / Apify / Zyte | Do not buy all three. Approve one only after a permitted source demonstrably requires remote browser/proxy capacity. | Bounded dynamic-page retrieval, never access-control circumvention. | Named blocked source, benchmark, terms review, concurrency cap. |
| Sentry | Create organization/project, invite engineering, configure alert owners. | Application exceptions and release-linked diagnostics. | Project slug, DSN in Secrets Manager, test event received. |
Official source priority
SEC EDGAR/IAPD, GLEIF, Companies House and regulator registers, maintained public disclosures, licensed bulk datasets, and Common Crawl historical captures before bespoke crawling.
Prohibited shortcuts
No authenticated LinkedIn scraping, CAPTCHA bypass, credential sharing, hidden-source redistribution, unsupported personal inference, silent entity merges, public contact exports, or provider terms ignored for speed.
6. Search, management, monitoring, and deferred activation
Private administration surface
Future CRM activation—explicitly deferred
Outreach boundary: outreach, sender setup, campaign tooling and CRM activation are paused. The Monday gate ends at harvesting, provenance, identity resolution, ranking, monitoring, search, review, pressure tests and reproducible receipts.
7. Private-data boundary and security
Public
Aggregate counts, system health, non-sensitive execution receipts, product documentation, and source categories. No personal contact details or licensed raw content.
Confidential
Named contacts, work email/phone/social URLs, provider-derived attributes, outreach history, source snapshots with restricted terms, suppression state, and exports.
Secrets
API keys, passwords, tokens, session cookies, private keys, recovery codes, DSNs with credentials, and raw export download tokens. Vault/Secrets Manager only.
8. Hour-by-hour launch schedule
| Window | Angelica | Engineering/fleet | Exit receipt |
|---|---|---|---|
| Monday hour 1 | Confirm vault, billing owner, incident contacts, MFA and recovery. | Verify the lane scope, repository state, protected-branch policy and existing local ingestion proof. | Named owners, vault paths, branch/commit and recovery receipt. |
| Monday hour 2 | Create/confirm AWS Organization plus isolated tides-dev. | Prepare least-privilege Terraform/OIDC plan; no static keys. | Account ID, region, role trust policy and plan output. |
| Monday hour 3 | Approve the unattended ceiling and alert recipients. | Install Budget Action deny, service quotas, no-NAT/no-always-on policies and repository HALT. | Tested deny, quota and halt receipts. |
| Monday hours 4–5 | Approve named dev resources and retention/backup settings. | Provision raw/derived storage, PostgreSQL, SQS/DLQ, ECR, Secrets Manager, logging and backups. | Object replay, DB migration/query, queue/DLQ, job and alert receipts. |
| Overnight | Available only for security/provider access escalation. | Run outcome/export/frequency/header defect tests and produce the production candidate. | Fail-closed test bundle. |
| Monday hour 6 | Create capped company API projects and store values only in the vault/Secrets Manager. | Run one bounded SEC/GLEIF connector job and model/provider smoke tests. | Secret-free account, cap, source, hash and unit-cost receipt. |
| Monday final hour | Review the escalation tree and recovery ownership. | Demonstrate backup restore, credential disable, branch protection and PR-only unattended workflow. | Named autonomy go/no-go; exact failures and fallback if no-go. |
9. Monday acceptance test
The autonomy handoff is green only if every required result below has evidence. A red item yields local/staging-only fallback, not a false readiness claim. The minimal tides-dev data plane and tested kill switches are Monday acceptance conditions; production-scale infrastructure is not.
Automatic no-go conditions
Secret/private-data exposure; archive writes without provenance; silent entity merges; exports bypassing suppression; public anonymous contact access; unbounded crawler concurrency; deployed/source SHA mismatch; data-loss recovery unknown; or a vendor/source used outside documented terms.
10. Angelica handoff packet
Send one compact receipt containing identifiers and decisions—not passwords or keys.
Unattended monthly ceiling and Budget Action ID:
Service quotas and no-NAT/no-always-on receipt:
Primary region:
Infrastructure-admin role ARN:
GitHub OIDC deploy-role ARN:
Runtime role ARNs:
AWS billing/anomaly alert recipients:
Password-vault collection name:
AWS secret paths created:
Raw bucket/Object Lock/PITR/backup receipt:
Queue/DLQ/container-job/alert receipt:
Repository HALT and credential-disable receipt:
Main protection and required reviewer receipt:
Cloudflare account/site + private hostname approval:
Apollo workspace + API entitlement:
PDL project + API entitlement:
OpenAI/Anthropic/X/Google/search project IDs and caps:
Sentry organization/project:
CRM/outreach state: DEFERRED / NOT ACTIVATED
Provider terms/retention exceptions:
Security/incident contact:
Unresolved blockers, owner, retry time:
Escalation matrix
| Problem | Owner | Response |
|---|---|---|
| Billing/account lockout | Angelica | Resolve with provider; provide ticket ID and retry time. |
| Architecture/code/test failure | Engineering / AI TIDES | Reroute after two failed approaches or 20 minutes without new evidence. |
| Source terms/data-rights ambiguity | Angelica + counsel owner | Disable only that connector; continue with cleared sources. |
| Secret/private-data exposure | Security owner | Stop affected flow; revoke/rotate; preserve audit evidence; assess scope. |
| Fable unavailable | OpenClaw owner | Self-audit and continue; record assumptions; queue Fable red-team review. |
| Launch verdict | Jason | Accept controlled beta, accept bounded exception, or no-go with explicit condition. |