PCProvider ComplianceAgent handoff
Canonical continuation route

Read the boundary before touching the build.

This handoff is the compact operating contract for any agent entering the Provider Compliance project from the public front door.

Read front door firstMachine manifestResearch index
Controlling decision

One evidence-backed case workspace—not one giant agent memory.

The model is a reasoning and drafting component. The case database, evidence, rules, approvals and artifact history are the authority.

Current case

Context first

Backstory, facts, unknowns and decisions are structured and versioned.

case_facts + case_history
Source control

Authority ranked

Official current requirements outrank guides, prior cases and model suggestions.

regulatory_authority
Examples

Fixtures only

Successful and incomplete cases stay separate from current factual retrieval.

evaluation_fixtures
Human gate

Approval required

Consultant and client decisions are explicit events, not inferred sentiment.

approvals
Required traversal

Read in this order.

Do not jump directly from a repository card to implementation.

  1. 01

    Product decision

    Scope and product boundary.

  2. 02

    Core findings

    Seven governing conclusions.

  3. 03

    Process

    Current workflow and hand-offs.

  4. 04

    Knowledge

    Namespaces and source authority.

  5. 05

    Pack evidence

    Edition and transformation controls.

  6. 06

    Market

    Company, competitors and wedge.

  7. 07

    Repositories

    Reuse/probe/defer decisions.

  8. 08

    Risks + next evidence

    Trust gates before building.

Non-negotiable rules

Do not silently cross these lines.

Public research gives orientation, not permission to access or publish private client evidence.

Required

Preserve provenance

  • Link material claims to current-case evidence.
  • Record source class and authority.
  • Keep tenants and cases isolated.
  • Ask when a material fact is unknown.
  • Retain approvals and supersession history.
Prohibited

Do not infer authority

  • Do not copy prior-case facts.
  • Do not treat internal guidance as current law.
  • Do not invent financial or operational inputs.
  • Do not publish raw client evidence.
  • Do not call an application successful without outcome proof.
Next evidence gate

Before implementation, obtain two cases and the live forms.

One successful end-to-end case, one incomplete case with its blocker, and the exact current Commission form packs create the minimum evaluation corpus.

NeededSuccessful case

Intake, revisions, approvals, submission, correspondence and outcome proof.

NeededIncomplete case

Exact stop point, blocker owner and expected next action.

NeededCurrent forms

Exact form-pack versions used in live practice.

DecisionPrivacy + hosting

Identity, region, model vendors, retention, deletion and incident response.

Current status

Discovery complete. Implementation not yet authorised.

Use the manifest and research library to frame the next scoped build only after the missing evidence and authority decisions are supplied.

Return to front door