AI Agent Control Plane · source of truth
Public docs for integrators and security reviewers. Versioned schema, product description, freshness rules, and data exposure stance live here, not in slide decks.
- Integrators: Write Intent schema → Check Write design
- Product / buyers: Salesforce Write Gate
- Security reviewers: Security & data handling
All documents below are the source of truth. LinkedIn and decks only point here.
On every wired mutate path: no agent write proceeds without Check Write. Orchestrator emits Write Intent; TC Protect™ returns Allow, Block, or Pause. Called gate: if the orchestrator skips the call, the write is not under Protect. TekCapitol™ does not MITM Salesforce or any system of record.
Stable documents
Write Intent v1
Versioned metadata every orchestrator must emit. Freshness and authorityStalePolicy included.
Salesforce Write Gate
Problem, how it works, data exposure, high-assurance mode, what you must wire.
Check Write v0
Emission path, decision API, audit log. Integrator technical note.
Security & data handling
What we see, what we do not, four access models, not SOC 2 yet.
Canonical URLs
| Artifact | URL |
|---|---|
| Docs home | https://tekcapitol.com/docs/ |
| Write Intent (human) | https://tekcapitol.com/docs/write-intent/ |
| Write Intent (JSON Schema) | https://tekcapitol.com/schema/write-intent/v1/write-intent.v1.json |
| Schema alias | https://tekcapitol.com/schemas/write-intent-v1.json |
| Salesforce Write Gate | https://tekcapitol.com/docs/salesforce-write-gate/ |
| Check Write design | https://tekcapitol.com/docs/check-write/ |
| Security one-pager | https://tekcapitol.com/docs/security/ |
write_intent.v2 at a new path under /schema/write-intent/v2/. write_intent.v1 remains stable at the URLs above.