PC Provider ComplianceResearch front door
Discovery baseline · 31 August 2026

A context-first operating system for provider applications.

Harrison's process is not one prompt. It is a regulated case workflow spanning client backstory, people, service scope, financial assumptions, evidence, policies, application answers, approvals and submission. This front door turns the complete discovery programme into one human-readable and agent-readable map.

Read the product decision Explore 208 companies Explore GitHub Machine manifest
208global companies/products
126GitHub repos screened
66deep system profiles
136live sitemap URLs checked
15preserved source files
18+research reports
01 · Product decision

One case workspace. One conversational front door. Several governed lanes.

The safe product preserves Harrison's judgement and client confirmation while moving durable state, evidence, approvals and version control out of chat memory.

Recommended

Consultant-led, evidence-backed application workspace

Propose, extract, compare, draft and validate—but abstain when material facts are missing and never submit without human approval.

Build

Durable case authority

  • Structured applicant backstory
  • Claim → evidence → requirement links
  • Consultant/client gap ownership
  • Versioned approvals and outputs
Avoid

Opaque general memory

  • Prior cases used as current facts
  • Incomplete answers becoming defaults
  • Static guidance outranking current forms
  • Silent filling of material blanks
02 · What the programme learned

Seven findings govern the build.

These are the points every agent should absorb before proposing architecture, prompts or automation.

01

Case context is product data.

No two applications are identical. Entity history, service choices, people, funding, geography, prior matters and the reason for applying must be explicit, versioned and evidence-linked.

02

Successful cases are fixtures, not memory.

Use proven end-to-end applications for evaluation, sequencing and quality patterns only after outcome evidence is attached. Never copy their facts or prose into a new applicant.

03

Incomplete cases are negative tests.

They are valuable for pause-and-ask, blocker routing and gap classification. Their unfinished answers must never seed defaults.

04

The master packs are versioned products.

Category 1–4 and 1–5 editions differ materially. Edition selection, inclusion rules, variables, transformations and validation need explicit manifests and deterministic receipts.

05

Regulatory authority outranks internal guidance.

The supplied guides are useful maps, but current legislation, Commission guidance and the exact current form pack control external requirements.

06

Human ownership is a safety feature.

Organisation-specific answers, client comprehension, consultant review and immutable approval history are core system behaviour—not friction to automate away.

07

The market gap is traceability.

Competitors sell consulting, documents and audit support. Few expose a durable workspace connecting backstory, evidence, decisions, approvals and regulatory versions.

03 · Current process reconstructed

The workflow is already coherent. The hand-offs are fragile.

The 9:25 process walkthrough and supplied operating instructions converge on this stage model.

  1. 01

    Intake + backstory

    Entity, history, categories, services, people, evidence, constraints and unanswered questions.

  2. 02

    Organisation design

    Propose role allocation, test suitability/concentration, then record explicit approval.

  3. 03

    Business viability

    Business plan, financial model, ramp, workforce and recruitment plan.

  4. 04

    Master-pack build

    Select the confirmed edition; populate, scope, brand, validate and create a Build Report.

  5. 05

    Application assembly

    Answer exact current form questions and link every material claim to evidence and authority.

  6. 06

    Gap routing

    Separate consultant-resolvable work from facts, decisions or documents only the client can provide.

  7. 07

    Review + finalisation

    Client review set, tracked decisions, mechanical finalisation and immutable final outputs.

  8. 08

    Submission lifecycle

    Receipt, Commission correspondence, outcome, renewal, variation and change-in-circumstance events.

04 · Knowledge architecture

Do not put everything in “memory.”

Every retrievable object needs a named source class and authority level.

Highest external authority

Regulatory authority

Current Act, Rules, Commission and Department guidance, and exact form packs with effective dates.

regulatory_authority
Workflow authority

Instructions

Versioned lane behaviour, source precedence, hard gates, delivery states and supersession history.

instructions
Reusable assets

Master templates

Pack editions, registers, variables, inclusion rules, transformations and validation contracts.

master_templates
Reviewed practice

Policy memory

Client-free standing rulings, defect patterns, methods and lessons promoted through human review.

policy_memory
Tenant + case scoped

Case facts

Current applicant intake, evidence, approved org chart, financial model and confirmed answers.

case_facts
Tenant + case scoped

Case history

Backstory, decisions, contradictions, assumptions, approvals, exclusions and state transitions.

case_history
Testing only

Evaluation fixtures

Frozen successful, incomplete and adversarial cases with expected outcomes and proof.

evaluation_fixtures
Orientation only

External research

Competitors, GitHub candidates, public company research and discovery observations.

external_research
05 · Master-pack evidence

Two editions, not one folder with extras.

The ZIP central directories and control registers establish a concrete versioning problem.

786Category 1–4 ZIP entries
852Category 1–5 ZIP entries
282normalised overlapping paths
173changed same-path files

Required bundle controls

  • Stable edition ID and source checksum
  • Canonical register and controlled vocabulary
  • Explicit inclusion and category rules
  • Variable schema with source and required state
  • Pre/post transformation token census
  • DOCX/XLSX structural validation
  • Category, jurisdiction and terminology gates
  • Output manifest, delta log and finalisation event
Open reconciliation: README versus variable counts, 31 versus 33 input fields, inconsistent clinical labels, referenced-but-absent control artifacts, legacy codes and macOS sidecar content.
06 · Company and market

A broad consultancy with an unclaimed software wedge.

The public company spans aged care, NDIS, ISO and business growth. Its current funnel remains consultation-led and quote-led.

Aged care

Registration + readiness

Application support, policies, governance, documentation, audit preparation and ongoing advice.

Official service page ↗
NDIS

Registration + systems

Registration support, policy setup, Practice Standards alignment and audit readiness.

Official service page ↗
ISO

Management systems

Gap analysis, implementation and audit preparation for ISO 9001, 27001 and 45001.

Official service page ↗
Live crawl136 / 136sitemap URLs returned
Current-site defect6pages contained “Aged Care Act 1997”
Current wording0pages contained literal “Aged Care Act 2024”
Trust surfaces3old Act, 1+ counters, wrong map target

Direct market references

Explore all 208 →

Competitor statistics and success rates are self-claims unless independently verified. Their presence here is market orientation, not endorsement.

07 · GitHub and SISO landscape

Borrow infrastructure patterns. Keep case authority custom.

Three independent lanes screened 126 repositories across regulated systems, document automation, and durable agents. No single repo owns the whole problem.

Explore structured repo recordsSee the five-repo decisionRead system deep dives
ReuseResearch and internal worker infrastructure

Foundry for external research; Runtime and Project OS for internal agent operations.

ProbeEvidence, parsing and privacy patterns

Evidence Engines contracts, pypdf, Docling and measured PII middleware.

DeferWorkflow platforms and CRM hosts

Temporal, LangGraph and SISOCRM only after simpler state and tenancy gates fail.

RejectLow-adoption turnkey claims

Do not outsource case authority or private application data to unproven PDF/compliance services.

Reuse · external researchSISO Foundry

Append-only observations, source identity and research provenance. Never the client case DB.

 Probe · contractsSISO Evidence Engines

Explicit JSON and evidence-gated export patterns for claim provenance.

 Reuse · internalSISO Agent Runtime

Bounded worker execution and checkpoints—not business-case state.

 Reuse · internalSISO Project OS

Tasks, missions and receipts for delivery operations.

 Defer · hostSISOCRM

Promising workspace kernel; tenancy, identity, audit and restore remain gates.

 Probe · documentsDocling

Mixed-document ingestion if real fixtures justify the dependency.

 Probe first · formspypdf

Local deterministic inspection and population of compatible PDFs.

 Probe · privacyPresidio

Defence-in-depth PII detection and redaction, never primary access control.

 Defer · workflowTemporal

Durable long-running execution if direct state transitions become inadequate.

 Defer · orchestrationLangGraph

Agent workflow framework; unnecessary until simpler persistence is disproven.

 Pattern · lineageOpenLineage

Useful event vocabulary; domain claim/evidence semantics remain custom.

 Pattern · regulationDocMCP Knowledge

Metadata and update patterns for regulatory packs; rebuild from Australian sources.
GitHub search boundary and additional probes

Searches covered tenant-isolated compliance workspaces, claim/evidence provenance, immutable audit logs, approval workflows, DOCX/XLSX transformations, PDF form filling, regulatory source versioning, PII redaction, aged care and NDIS compliance.

Additional pattern-only candidates include replayable RAG, evidence-ledger hashing, CloakLLM and Wirken. Repository self-claims remain unverified until source and deployment probes run.

08 · Minimum safe architecture

The smallest system that preserves trust.

Custom where meaning and authority live; reusable where infrastructure is generic.

Missing inputUnsupported claimStale authorityWrong categoryEvidence expiryContradictionClient blockerConsultant taskCross-tenant leakageUnapproved finalisation
09 · Risks and immediate corrections

Fix trust surfaces before selling the system.

These are verified discovery findings or explicit decision gates—not a legal opinion.

RiskWhy it mattersResponse
Old legislative references

Six sitemap pages still contain “Aged Care Act 1997.”

Correct and reconcile all live/indexed content.
Broken public proof

Metrics render as 1+ and the Sydney map target points to Karachi.

Repair before using the site as product proof.
Source-pack drift

Internal mappings and asserted rules cannot outrank current official forms.

Freeze, version and reconcile against exact packs.
Client data exposure

Applications contain identity, screening, qualification and financial material.

Tenant isolation, least privilege, encryption, retention and deletion controls.
Hidden assumptions

Financial or operational blanks can become unsupported claims.

Record proposed values and require explicit confirmation.
Case contamination

Reusable memory currently contains active-case names and unrelated downloads.

Namespace, quarantine and enforce clean-slate retrieval.
10 · Research pack library

One front door, with the deeper evidence labelled.

Public-safe summaries are available here. Private working papers and source evidence remain in the controlled project workspace.

Start hereExecutive decision

Product boundary, positioning and Phase 0 gate.

 ProcessWorkflow deep dive

Current stages, hand-offs, gap routes and review states.

 KnowledgeMemory architecture

Authority classes, case backstory and successful/incomplete fixtures.

 DocumentsMaster-pack findings

Edition differences, controls and reconciliation issues.

 MarketCompany + competitors

Website crawl, public trust audit and strategic wedge.

 Global market208-company synthesis

Seven archetypes, feature frequency and white space.

 DirectoryCompany explorer

Filter all 208 companies/products and 30 workflow profiles.

 TechnologyGitHub repo explorer

Cross-lane records, metadata, mechanics, gaps and verdicts.

 ArchitectureMinimum-repo decision

Why five repositories beat a fifteen-platform stack.

 IndexAll research packs

Pack-by-pack purpose, status and public boundary.

 AgentsCanonical handoff

Traversal order, source rules, prohibited assumptions and next actions.

 Machine-readableResearch manifest

Claims, entry points, authority and publication contract.
Smallest high-value next move

Ingest one proven success and one honest failure.

De-identify and preserve one application from intake through Commission outcome, plus one incomplete case with its exact blocker. Use them to prove the case schema, gap routing, source precedence and evaluation harness before building a polished client portal.

Open agent handoff