Start in five minutes
TekCapitol builds Check Write™ for consequential AI agent actions. One API call before the write. Allow, Pause, or Block. Your code still performs the write.
- Open Check Write™ Sandbox (no key) or get an API key (email OTP: subject Your TekCapitol™ Check Write™ access code)
- Send a Write Intent
- Receive Allow / Pause / Block
- Perform the write only on Allow
Linear developer path: Check Write™ Sandbox → API key → this reference. Scenario demos: /industries/ (eight flagship domain demos; full scenario library is internal).
Quickstarts
Developer quickstart
Send Write Intent, read the decision, write only on Allow. Architecture comes after.
Check Write™
Decision API, Allow / Pause / Block, auditId.
Write Intent v1
Versioned metadata envelope for the intended action.
Write Intent JSON Schema
Machine-readable write_intent.v1.
Check Write™ response schema
Machine-readable check_write response v1 (reason, reason_code required).
TC360®
├── TC Diagnose™
├── TC Fix™
└── TC Protect™
└── Check Write™
Developers typically enter through Check Write™. Customer owns execution. Called gate: skipping the call means that write is not under Protect. TekCapitol does not MITM the system of record.
Deeper reference
Salesforce Check Write™ integration
Problem, how it works, data exposure, high-assurance mode, what you must wire.
SAP Check Write™ integration
Problem, how it works, data exposure, high-assurance mode, what you must wire.
Snowflake Check Write™ integration
Problem, how it works, data exposure, high-assurance mode, what you must wire.
ServiceNow Check Write™ integration
Problem, how it works, data exposure, high-assurance mode, what you must wire.
Check Action
Runtime engine under Check Write™: authority, intent, delegation, blast radius.
Nuanced Policy Gates
Bias, drift, context, explanation quality, and more. Prefer Pause when confidence is low.
Policy picker
Business questions → writePolicy, unknownKeyPolicy, emit cheat sheet.
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 Check Write™ integration | https://tekcapitol.com/docs/salesforce-write-gate/ |
| SAP Check Write™ integration | https://tekcapitol.com/docs/sap-write-gate/ |
| Snowflake Check Write™ integration | https://tekcapitol.com/docs/snowflake-write-gate/ |
| ServiceNow Check Write™ integration | https://tekcapitol.com/docs/servicenow-write-gate/ |
| Check Write™ design | https://tekcapitol.com/docs/check-write/ |
| Check Action design | https://tekcapitol.com/docs/check-action/ |
| Nuanced Policy Gates | https://tekcapitol.com/docs/nuanced-policies/ |
| Policy picker | https://tekcapitol.com/docs/policy-picker/ |
| 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.