C³ CONTROL ASSURANCE / PARTNER GUIDE v1.2
Check whether human-defined AI rules actually hold.
Customers and governance or implementation partners decide what an AI agent may do, where it must stop and when it must return to a human. C³ helps express those decisions as checkable conditions and separately inspects the specified implemented behavior.
The downloadable partner and service PDFs are currently Japanese-language documents. This English web guide does not represent them as English PDFs.
A partnership, not a required reseller program
C³ does not replace the customer's governance partner or implementer. Control Design Review and Control Condition Gap Check can be commissioned separately, or connected only when both are needed. A partner does not have to choose the service before introducing the customer.
Customer / governance partner
Chooses delegation, stop, escalation and approval rules. People retain final decisions.
Implementation team
Implements and repairs approval, authority, logging and recovery in agents, workflows and systems.
C³ inspection
Fixes target version and declared conditions, checks selected paths and variants, and records bounded evidence.
Observed control ≠ delegable scope ≠ runtime permission
Two independent service paths
AI Agent Control Design Review
JPY 30,000 excluding tax / one flow
Organize the human's delegation, stopping and handoff rules into implementation and QA conditions. The output is a design review, not an executed runtime inspection.
Control Condition Gap Check
JPY 600,000 excluding tax / standard engagement
Typically one release, one delegation condition and one declared control, up to 12 cells / 36 trials in 5–10 business days. Probe missing approval, changed targets, expired conditions and alternate paths. Multiple controls, paths or custom connectors require separate estimates.
A separate JPY 50,000 small-scope plan checks existing responses and customer-provided logs. It is not the standard runtime-path assessment.
Both services can be used independently. Review findings never automatically issue execution permission.
Eight illustrative human-defined conditions
These examples are not C³-prescribed policies, professional advice or observed customer findings.
CASE 01
Customer email
Human-defined rule: Send only the approved body to the approved recipient.
Variant to check: Recipient or message changed after approval; a send without approval.
CASE 02
Production deployment
Human-defined rule: Deploy only the exact human-approved commit.
Variant to check: HEAD changes after approval; a different branch or artifact.
CASE 03
Payments and orders
Human-defined rule: Use only the selected amount, counterparty and approval.
Variant to check: Different amount or payee; missing approval record.
CASE 04
Customer data updates or deletion
Human-defined rule: Change only the named customer, fields and count.
Variant to check: Different ID, unauthorized field or switch to deletion.
CASE 05
Recruiting support
Human-defined rule: AI organizes information; people make final decisions and send notices.
Variant to check: An external notice or decision-like action without human review.
CASE 06
Web, advertising and policy publication
Human-defined rule: Publish only the human-approved version.
Variant to check: Text replaced after approval or sent to another URL/channel.
CASE 07
Refunds and compensation
Human-defined rule: Prepare candidates within the rules; escalate exceptions.
Variant to check: Out-of-scope case, changed beneficiary or premature execution.
CASE 08
External tools and APIs
Human-defined rule: Use only the approved tool, operation, target and payload.
Variant to check: Different tool/target, altered payload or retry route.
From design review to evidence, when both are needed
1
Prepare
Identify the target version, intended delegation and existing evidence.
2
Confirm human rules
Who approves, what may be delegated, and when execution must stop.
3
Define testable conditions
Map the human's rules to control, delegation and verification conditions.
4
Freeze scope
Fix the release and one declared control for the agreed inspection.
5
Challenge the boundary
Test missing approvals, changed targets and alternative routes.
6
Recheck
Run the same witness after an implementation correction, where agreed.
7
Deliver the record
Separate observations, counterexamples, undefined and unobserved scope, with evidence.
An allow-side match is not a license to delegate. Results are restricted to the recorded version, witnesses and evidence; unobserved or UNDEFINED areas are not silently marked safe.
Read delegation-condition evidence samples →Referral fee conditions — only when eligible
A referral fee is not necessary for ordinary governance or implementation collaboration. It applies to an eligible first Control Condition Gap Check engagement after C³ receives the customer's payment.
- Referral fee
- 20% of the excluding-tax fee actually received by C³ for the customer's initial Control Condition Gap Check.
- Trigger
- The customer completes the qualifying payment to C³.
- Eligible engagement
- One initial Control Condition Gap Check only. Design review is not fee-eligible.
- Referral window
- Six months after referral registration.
- Contracting party
- The customer contracts directly with C³.
- Pricing and estimates
- Set by C³. A referrer has no agency, contracting or discount authority.
- Later engagements
- Renewals and repeat inspections are excluded.
- Legal and professional eligibility
- Payment only where law, professional standards, employer policy and customer contracts permit.
- Inspection independence
- Referral fees do not affect method, findings, deliverables or Verify ID content.
Payment timing, competing referrals, cancellations/refunds and tax arrangements require separate terms before operation. Each party remains responsible for disclosures required by law, professional rules, employer policies or customer agreements.
What to share at the first discussion
- Target version: the AI system, agent, workflow or release.
- Human rules: permitted delegation, stopping conditions and approvers.
- Existing evidence: specifications, settings, tests, logs and review records.