TouchwardenDiscuss a paid pilot →

Agent-first · Customer-local · Assisted preview

Build with AI.
Keep your business promises.

Your agent can change the implementation. It should not silently change what a price, payment or booking promises your customer.

Start with one rule you actually care about. A human approves its meaning. Touchwarden gives your coding agent the applicable rules and checks covered changes against the approved base.

Request a scoped pilotSee the agent workflow

Not an AI “looks good” verdict. Not whole-application verification.

Choose a consequential promise.

Pricing

Does the approved discount composition still hold after a checkout change?

Paid orders

Should an address-only edit preserve the customer's quoted promotions?

Bookings

Can customers still see and select every offered appointment?

Examples of rules to scope—not claims that all commerce or booking applications are already covered.

Inside the agent you already use.

  1. Connect the local tools. A private Claude Code plugin, or local stdio MCP configuration for Claude Code, Cursor and Codex. No public marketplace listing or published npm install is promised yet.
  2. Propose one rule. Use your existing agent to inspect explicitly agreed source. Discovery may send source to your agent's model provider under its terms; Touchwarden does not proxy that inference.
  3. A human owner reviews. Scope, legitimate changes and trusted boundaries must be agreed. Put reviewed rules on the protected base. An agent answer or exported JSON is not approval.
  4. Edit, then check. Read rules before covered edits; run the local check before finishing. Failures remain failures. Protected weakening requires owner review.
/touchwarden:protect
/touchwarden:check
/touchwarden:pilot

Connection is not protection. The status tool explicitly distinguishes missing rules, pending owner review and configured rules. Configured proof tiers are not fresh verification results.

Agent reminders are guidance, not a sandbox or an unskippable merge gate. A separately reviewed, protected CI workflow is needed for merge enforcement.

Paid founder-assisted pilot · Quote agreed before payment

One repository. One rule. A real decision about value.

  • Choose the business promise and an independent human approver.
  • Agree what is covered and what remains trusted or unverified.
  • Exercise an unsafe change that must be refused and a legitimate change that must pass.
  • Help wire the local agent and plan the protected CI boundary.
  • Review the evidence and whether this earns a place in your workflow.

Price, deliverables, support and terms are agreed in a scoped quote. Local checks do not require a Touchwarden account or payment. Connected subscriptions and checkout are not live.

Ask for a pilot quote

The first conversation needs no repository access. The email draft asks for stack, a plain-language promise, owner and timing only. Do not send code, logs, secrets, screenshots, private repo links or customer data. Review sensitive policy prose before sharing.

What the evidence means.

Bend proofs cover named decision laws. Compilers, source-to-policy interpretation, adapters, databases, DOM measurements and effect coverage remain separate trusted or tested boundaries. A passing covered check does not prove every application path.

This is an assisted development preview, not an established production integration or independently validated customer ROI. Full native integrations, public distribution and licensing review remain release work.