Point One Zero Platform architecturev11 · generated viewSign in to edit
Platform Layers › L3 Knowledge

L3 Knowledge

Where this layer sits on the architecture; the client plane band to its right shows the values it reads.

P1Z Platform ArchitectureOne reusable platform, one customization plane, equal partners: the platform is what P1Z builds once; the plane is what makes it a client's own · v2.5P1Z REUSABLE PLATFORMbuilt once, every client runs these same seven layers, unchangedCLIENT CUSTOMIZATION PLANEthe only per-client build, values, never codeLifecycle: PLAN (EA assessment fills the binding) → RUN (operate)1. ExperienceAMBIENT · CONVERSATIONAL · CROSS-CHANNELChatWeb AppDesktopMobile AppVoicePhone / Call CenterEmbedded in ToolsMCP HostsClaude, CopilotOutput & Format Rendererstructures from Knowledge · templates from the PlaneShared UI Coreone core behind every P1Z shell · cross-channelcontinuityChannel Mix & Notificationschannels on/off per client · proactive rulesFeedback Captureedits & rejections → eval storeC1. ExperienceVALUES, NEVER CODEChannel Mixon/off per audienceHouse Templatesbranding & layoutsOutput FormatsTone & LanguageNotification RulesEmbedded Surface Selectionwhich work toolsNORTH-FACING PLATFORM MCP GATEWAY, the whole platform exposed as an MCP SERVER to any host above: agents, use cases and UI resources as tools; allcode and business logic stays server-hosted.Per-tenant endpoint · tenant auth · host allow-list2. SolutionCLIENT-BLIND CODE · CLIENT-AWARE EXECUTIONOrchestratordeterministic, routes, gates, never authorsBusiness Agentsjudgment under guardrails; face the gatesWorkflowsdeterministic multi-stepCopilotshuman-driven assistSkillsone per use case, on demandDomain Rule Libraryimplements what Knowledge declares, computed once, cited everywhereSubagent Workersinternal; bounded summary contractsDetermination rule: any task with a testable right answer is deterministic code. Agents get judgment only, the last resort, not the firstdraft.C2. SolutionVALUES, NEVER CODEUse-Case Activationwhich agents are onOrchestration Modeserial vs parallel per use caseHITL Placementwhere humans reviewCustom Workflow Compositionreusable agents, never new codeOverride & Exception RoutingOverlay Selection3. KnowledgeCLIENT-BLIND · VERSIONED RELEASES ONLYIndustry OntologiesPE today, healthcare next, stable IDsFunctional Ontologiescross-industry: finance ops, legal, reportingP1Z Benchmarkseval outcomes, gate metrics, cycle-time normsPromotion Gateanonymize → aggregate → rights check → human review → versioned releaseCurated Consulting Benchmarksage-old priors as versioned dataC3. KnowledgeVALUES, NEVER CODEOntology Version Pinthe exact release this client readsOverlay Selectione.g., growth equityStage & Gate Name Mappingthe client's languageBenchmark Scope & Data-Rights Clausewhat telemetry may be promoted4. Intelligence (the AI layer)VENDOR-AGNOSTIC · SWAPPABLEModel Routerthe portability boundaryFoundation LLMsSmall Language ModelsEmbeddingsRerankersThis thin layer absorbs model progress, models upgrade, nothing above changes. AGI-readiness is a one-layer swap, not a rebuild.C4. IntelligenceVALUES, NEVER CODEModel Tier PreferenceCost Ceilingsthe router enforces themLatency TargetsApproved-Vendor ListData Sensitivity Boundarywhich classes reach which tier5. IntegrationAGENT TOOL CALLS & API CALLS ENTER HERESouth-Facing MCP Tool Serversplatform acts as MCP CLIENT here, one server per source; permissions onceAPI Gatewayoutbound external API calls; rate limits, retriesConnector Librarypre-built: Egnyte, SharePoint, Airtable, APIsSync EngineSource Catalogsources · access rulesETL, Batch & Streaming TemplatesSchema-Mapping ToolkitDead-letter HandlingMiddleware between everything above and the data below. A missing connector is BUILT into the library and SELECTED on the plane.C5. IntegrationVALUES, NEVER CODESource System SelectionCredentials & OAuth GrantsData ContractsField Mappingsclient schema → taxonomySync Schedules & ModesCustom Connector Selectionfrom the library6. Data & DocumentsPER-TENANT ISOLATION · DATA ENGINEERINGVector DB ServiceDocument Store ServiceData Warehouse ServiceRetrieval APIsIndexing & Taxonomystructures from KnowledgeSystems of RecordERP, CRM, fund adminDocument SourcesVDR, SharePoint, emailUnstructured Datanotes, transcripts, recordingsExternal Data Providersmarket & benchmark feedsTenant stores are reusable templates; dashed boxes are the SOURCE ESTATE they front, reached only through Integration (L5).C6. Data & DocumentsVALUES, NEVER CODETenant Store Instancesthe client's actual dataSource Estate Inventorytheir SoRs, VDRs, warehouses, feedsDocument Taxonomy Mappingtheir docs → the taxonomyData Residency & RegionsRetention & Legal Hold7. Environment (the Harness)BUSINESS-BLIND · SELF-OPTIMIZINGAgent Loop & Run Contractsend state + token budget; over-budget = killGuardrail Mechanics4 locks: instructions < hooks < scopes < gatesSession & Memory Machinerycontext packs, compaction, memory storesObservability & Eval Infracontent-blind traces; eval runners; A/BIdentity & Tenancyservice identities; isolation tests in CICI/CD, ADLC & SSRA Skeletonrepo templates: constitutions, skills, agent defs; sandbox →eval gate → promotion → registry deploySecrets & KMSper-tenant keysSRE & Incident Opsrunbooks, DR, on-callFuture-proofed and model-agnostic by construction. Self-optimizing via the operational loop, every tuning is a versioned config change throughCI; silent drift is a defect.C7. EnvironmentVALUES, NEVER CODETenancy & Account MappingIdentity ProviderEntra / Cognito / OktaToken Budgetsper use caseGate Approver RolesAlerts & Escalation TimersNo code in the plane, values only. Custom logic is a Solution-layeroverlay, SELECTED here.slotsandvaluesKNOWLEDGE LOOP, telemetry & evals, gatedOPERATIONALLOOPlearns how to run -versioned, never silentDeferred and open items are not drawn and never lost: they live on the Decision Register page, with activation triggers.How to read this diagram• Left column: what P1Z builds once and every client reuses. Right column: the values one client fills in. The double-headed connectors between them are that exchange. Samestructure on both sides, only the contents differ.• Two MCP boundaries. The north gateway (between layers 1 and 2) is where hosts like Claude or Copilot connect; all code stays on the server. The south tool servers (layer5) are where agents reach data. Tenant identity is checked at the north, source permissions at the south.• Read top to bottom to follow a request. Build bottom to top; setup starts at layer 7. The knowledge loop promotes gated telemetry into benchmarks. The operational looptunes the harness. The two loops never mix.• Agents live in layer 2 and are reused unchanged; the plane only switches them on and arranges them. No code ever enters the client column.Point One Zero · generated view, scripts/generators/build_p1z_arch.py · v2.4 · seven layers + client plane

L3 Knowledge CLIENT-BLIND · VERSIONED RELEASES ONLY

P1Z's knowledge asset, declares what is true, never how to act. Three shelves with different lifecycles, one release discipline: continuous ingestion, versioned release; engagements pin versions.

  • Industry ontologies, PE today, healthcare next; versioned, stable IDs
  • Functional ontologies, cross-industry: finance ops, legal, reporting; the reuse multiplier
  • P1Z benchmarks, the differentiated asset: eval outcomes, gate metrics, cycle-time norms, plus curated age-old consulting priors
  • Promotion gate on all telemetry: anonymize → aggregate → contractual-rights check → human review → versioned release; classification is inherited, restricted-class content never reaches the shared shelf

Boundary test: no instructions, no orchestration, no client-identifiable values, ever.

Plane parameters: overlays · ontology version pins · benchmark access scope

Client-specific configuration for this layer is specified band by band in Client Delivery, C3 spec: every input with its binding key, generated artifact, and verifying check.

Component reference

Industry Ontologies

The versioned truth of an industry: concepts, relationships, document taxonomy and declared business rules that hold across firms.

ImplementationReleased as versioned, stable-ID packages from the ontology repo; engagements pin a release through the C3 ontology version pin and read it as read-only.

Functional Ontologies

Cross-industry functional knowledge: finance operations, legal, reporting. The reuse multiplier across industries.

ImplementationSame release discipline and pinning mechanics as the industry shelf.

P1Z Benchmarks

The differentiated benchmark shelf: eval outcomes, gate metrics, and cycle-time norms accumulated across engagements.

ImplementationFed exclusively through the promotion gate; what any client's telemetry may contribute is bounded by their data-rights clause (C3). The eval and observability tooling is table stakes; this accumulated, promotion-gated data is the differentiated asset.

Curated Consulting Benchmarks

Age-old consulting priors, curated by people and versioned like everything else on the shelf.

ImplementationEnter through the same release train as promoted telemetry; never client-attributable.

Promotion Gate

The only path telemetry ever takes into shared knowledge.

ImplementationAnonymize, aggregate, contractual-rights check, human review, versioned release, in that order. Classification inheritance is enforced here: restricted-class content never reaches the shelf. Sealed from the operational loop.

← L2 SolutionL4 Intelligence →