C³ ANCHOR / GOVERNANCE & IMPLEMENTATION PARTNERS

Partner to check whether human-defined AI rules actually hold.

Customers and partners decide which work may be delegated to an AI system, when it must stop and who makes the final decision. C³ helps express those rules as checkable conditions and observes whether the implementation preserves them.

This is not a mandatory reseller program. Design review and gap checking may be used independently or connected when a case benefits from both. A referral does not require selecting one service upfront.

Free pre-screening →Design review →Formal gap check →Partner guide → (Japanese source)

The current PDF service and partner guides are in Japanese. This English page does not represent those files as English translations.

Who this partnership is for

AI governance and institutional design consultants

Business process, DX and risk-management consultants

System integrators, AI system developers and agent vendors

QA, platform, DevOps and security teams

Internal AI adoption, legal, compliance and business teams

Two distinct collaboration services

DESIGN AND QA CONDITIONS

AI Agent Control Design Review

JPY 30,000 excluding tax / one flow

From documents, specifications and code, turn human-selected delegation and stop rules into required control properties, implementation candidates and post-implementation QA conditions. A two-page review sheet; no runtime inspection.

Discuss a design review →

BOUNDED RUNTIME INSPECTION

Control Condition Gap Check

JPY 600,000 excluding tax / standard engagement

Freeze the exact target version and declared condition, observe normal and changed-condition execution paths, and preserve supported results, counterexamples, UNDEFINED and unobserved scope with evidence. Standard scope: one release, one delegation condition, one control, up to 12 cells / 36 trials.

Discuss a formal inspection →

The JPY 50,000 small-scope plan is a different evidence method based on existing responses and customer-provided logs, not the standard runtime-path assessment.

Separate policy choices, implementation and inspection

Customer / governance partner

Define the delegation, stop, escalation and approval rules.

Implementation team

Implement or remediate those rules in the system, workflow or agent.

C³ inspection role

Map the declared conditions into evidence questions and inspect the agreed implementation path.

1
People define the rules
The customer and their governance partner decide what to delegate, where to stop and who approves.
2
C³ maps them to checkable conditions
Turn written rules into control, delegation and verification conditions without taking over policy authority.
3
The implementation team builds or remediates
The customer, systems integrator or engineering vendor owns implementation and changes.
4
C³ checks observed behavior
Test selected normal and changed conditions, including possible bypasses, mismatches and missing evidence.
5
The recipient reviews the bounded record
Return evidence, results and an inspection record with its target version and limits; no automatic runtime Permit.

Published examples

Public source reviews and live observations have different evidence classes. Consult the individual record before representing a conclusion as tested.

Email approval design review → (Japanese source)

Tool pre-execution design review → (Japanese source)

Browser Use live demonstration → (Japanese source)

Delegation-condition output samples → (Japanese source)

Eight illustrative delegation conditions

These are examples of rules the customer might choose, not legal advice, generally recommended policies or actual customer findings.

CASE 01

Customer email

Human-defined rule: Send only text a person approved, to the recipient they approved.
Conditions to bind: Approver, approved body, destination, and approval validity window.
Changed-condition probe: Change the body or recipient after approval; request a send without approval.
How to read the observation: If the altered send succeeds, record the counterexample. Re-approval before sending may be evidence of control preservation within the observed case.

CASE 02

Production deployment

Human-defined rule: Publish only the approved commit.
Conditions to bind: Approved SHA, environment and approving principal.
Changed-condition probe: Change HEAD after approval or submit a different branch or artifact.
How to read the observation: Inspect whether any path deploys a different target under the old approval.

CASE 03

Payment and procurement

Human-defined rule: Act only within customer-defined amount, recipient and approval conditions.
Conditions to bind: Amount, payee, approver and invoice or order identity.
Changed-condition probe: Change amount, payee or the approval record.
How to read the observation: C³ does not choose monetary policy; it checks whether the customer's chosen boundary is preserved.

CASE 04

Customer data updates or deletes

Human-defined rule: Modify only the specified customer, fields and record count.
Conditions to bind: Target ID, allowed fields, operation and count ceiling.
Changed-condition probe: Different customer, unauthorized field or operation changed to delete.
How to read the observation: Observe whether the system stops when the declared scope is exceeded.

CASE 05

Hiring and HR support

Human-defined rule: AI may organize information and suggest options; a human makes final decisions and controls external notices.
Conditions to bind: Allowed AI steps, human-handoff steps and external notification approval.
Changed-condition probe: Notify applicants or carry out a final-decision equivalent without human confirmation.
How to read the observation: C³ checks an agreed authority boundary, not the merits of an employment decision.

CASE 06

Publishing a website, advertisement or terms

Human-defined rule: Publish only the approved version.
Conditions to bind: Approved version, person, destination and permissible changes.
Changed-condition probe: Change wording or publication channel after approval.
How to read the observation: Inspect whether publishing stops when approval no longer matches the outgoing content.

CASE 07

Refunds and customer compensation

Human-defined rule: AI may prepare options within customer policy; cases outside it return to a human.
Conditions to bind: Case, eligible conditions, authority and final actor.
Changed-condition probe: Ineligible case, different customer or execution before approval.
How to read the observation: Search for an execution path that exceeds the customer's policy rather than judging that policy's values.

CASE 08

External tools and APIs

Human-defined rule: Execute only the permitted tool, operation, target and payload.
Conditions to bind: Tool identity, operation, target, payload constraints and approval binding.
Changed-condition probe: Different tool or target, payload changed after approval, alternate retry route.
How to read the observation: Compare the agent's proposal with the actual effect target and parameters immediately before execution.

IF AN ELIGIBLE CUSTOMER REFERRAL IS INVOLVED

Initial inspection referral fee: 20% of the excluding-tax amount actually received.

Referral compensation is not required for ordinary governance or implementation collaboration. It applies only if a registered referral results in the customer's first Control Condition Gap Check contract and payment to C³.

Referral fee: 20% of the excluding-tax amount actually received by C³ for the customer's first Control Condition Gap Check.
Fee trigger: Payment of the eligible fee from the customer to C³ has completed.
Eligible engagement: One initial Control Condition Gap Check. The design review is not eligible for this referral fee.
Referral validity: Six months from referral registration.
Service contract: Between the customer and C³, not the referrer.
Referrer's authority: No agency, contracting or unilateral discount authority.
Repeat or follow-up checks: Not included in the referral-fee calculation.
Eligibility: The referrer must be entitled to receive the fee under applicable law, professional obligations, employment rules and customer contracts.
Inspection independence: Referral arrangements do not change the method, observations, deliverables or contents of a Verify ID.

Payment timing, duplicate referrals, cancellations, refunds and tax treatment must be fixed in separate referral terms or an individual agreement before actual referrals begin. Each party remains responsible for disclosures required by law, professional rules, employer policy and contractual obligations. These administrative arrangements cannot change the inspection standard or results.

Read the detailed public partner guide → (Japanese source)

Frequently asked questions

Does C³ set the policy for the customer?

No. People choose what the AI may do, when it must stop and who must approve. C³ helps turn that decision into observable conditions and checks the bounded behavior.

Does this compete with governance consultants or system integrators?

The roles can be separated. Partners design rules and implement systems; C³ reviews checkable requirements and inspects the behavior of specified controls.

Is a Control Design Review already a tested result?

No. It identifies conditions from documents and source material. The runtime test and formal result are separate.

Is this a general vulnerability scan, audit or certification?

No. This checks specific declared controls on an agreed target and path. Unobserved conditions and insufficient evidence are not converted into a safe result.

Can C³ inspect a system it previously helped review?

Its design involvement must be disclosed and kept separate from the test. Evidence and recheck procedures can be retained so the recipient can evaluate the basis.

When should a partner contact C³?

If the rules are unclear, use free pre-screening; if implementation conditions need drafting, request a design review; if the control is implemented and testable, discuss a scoped gap check.

Begin with one workflow and its human-defined rule.

The free pre-screening can identify two or three important routes or candidate checks from a single workflow, without requiring credentials, raw production data or a paid commitment.

Free pre-screening →Design review →Formal inspection →