2SOLID AI — Cortex Edition
Cortex Trace
The outreach edition of the control plane. Enrollment pipelines, compliance-gated contact, deliverable drafts, and a tenant-scoped cloud spine — the instrument our own operations run on.
Talk to Engineering§01 — CLASSIFICATION
An operations spine, not a mail-merge tool.
Trace runs outreach as a governed pipeline: contacts enroll through tracked stages, every contact attempt respects jurisdiction-aware calling windows, disclosures are enforced before send, and deliverables land as drafted artifacts with evidence attached. It is the system 2SOLID AI runs on — shown here as a reference deployment.
§02 — THE PIPELINE
Enrollment to deliverable, gated at every consequential step.
Each stage is a verified surface — compliance is structural, not a checklist applied afterward.
| 01Enrollment | progress-tracked pipeline | contacts move through stages; every transition is recorded |
|---|---|---|
| 02Contact windows | assist mode | jurisdiction-aware calling windows gate outbound contact before dispatch |
| 03Disclosure | FTC verbal + overlay, fail-closed | video assets burn in the AI label; audio assets speak the line first — generation refuses otherwise |
| 04Outbound channels | official APIs only | publishing refuses without an official adapter — no scraping shortcuts |
| 05Deliverables | drafted artifacts in SQLite | proposals, reports, client-ready documents — not chat replies |
| 06Cloud spine | trace-cloud | multi-tenant REST backend — inbound webhooks fold into live enrollments |
§03 — HARDENED BY DEFAULT
The security posture is part of the product, not a bolt-on.
Filesystem confinement
Workspace file operations are realpath-confined to the project root — symlink escapes, dangling links, and encoded traversals all refuse before the write.
Egress gating
Every outbound call — headless completes, comment classification, outreach variants — passes the same destination and sensitivity gates.
Staged-job quarantine
Jobs drained from other contexts run flagged as staged; consequential tools refuse unattended unless the class was pre-approved.
Ingest ignore-chain
The ingest pipeline honors the full gitignore chain — .env.local-class secrets cannot be silently pulled into the brain.
Signed update feed
Release manifests and installers are artifact-verified pre-publish and feed-verified post-publish — anonymous, exactly like a client updater.
Tenant isolation
The cloud spine is tenant-scoped end to end — memory, enrollments, and artifacts never cross the tenant boundary.
§04 — DEPLOYMENT MODEL
Internal instrument, corporate deployments by request.
Trace is the system we run our own operations on. It is not a self-serve product — corporate deployments are scoped with our engineering team.
Self-serve tools
Sign up, connect your accounts, send.
- Compliance is your problem — disclosures, windows, consent
- Black-box sending with no audit trail
- Data leaves your boundary to feed the platform
Cortex Trace
Deployed instrument, scoped with engineers.
- Compliance enforced in the pipeline — it refuses, not warns
- Every consequential action carries an evidence receipt
- Tenant-scoped cloud spine — your data stays yours
See the instrument that runs our operation.
Corporate deployments are scoped with our engineering team — tell us what your outreach operation looks like.