Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.uselayerup.com/llms.txt

Use this file to discover all available pages before exploring further.

24 — Reference appendix.

Reference material for technical diligence: glossary, object index, tool-pattern index, action registry, role × permission matrix, event taxonomy, and integration / rollout checklists. All entries are generic platform contracts.

24.1 Glossary

For full definitions, see §4. Selected entries:
TermDefinition
SubstrateThe platform itself; the unified plane on which agents and humans operate.
PlaneOne of the eight horizontal layers (Experience, Reasoning, Logic, Ontology, Data, Model Gateway, Action, External SoR).
System of recordAn external authoritative system Layerup integrates with.
ObjectA typed business entity in the Ontology.
MarkingA non-bypassable label attached to data; gates access.
PurposeA declared reason for accessing data; required for tool calls and human reads.
DecisionA typed verdict produced by an agent or human reviewer; first-class object.
ActionA typed intent to mutate a system of record; lives on the Action Plane.
AgentRunOne bounded execution of an agent against an input object.
EvidenceSpanA typed citation linking a derived property or Decision back to source bytes.
Capability laneA typed slot in the Model Gateway routing table.
PDPPolicy Decision Point; evaluates every tool call.
Idempotency keyDeterministic key over the action’s intent; commit at most once.
Drift sigmaStandard-deviation distance of current eval window from trailing baseline.
ReplayReconstruction of a run given runId and ontology version.
Break-glassPurpose-tagged, MFA-stepped, time-limited grant for incident response.

24.2 Object schema index

All 28 objects of the Insurance Ontology (§5):
#GroupObjectAnchor
1PartiesInsuredo-insured
2PartiesBrokero-broker
3PartiesClaimanto-claimant
4PartiesUnderwritero-underwriter
5PartiesAdjustero-adjuster
6Master dataPolicyo-policy
7Master dataCoverageo-coverage
8Master dataEndorsemento-endorsement
9UnderwritingSubmissiono-submission
10UnderwritingQuoteo-quote
11UnderwritingRiskAssessmento-risk
12UnderwritingPricingo-pricing
13UnderwritingBindingAuthorityo-binding
14ClaimsClaimo-claim
15ClaimsLossEvento-loss
16ClaimsExposureo-exposure
17ClaimsReserveo-reserve
18ClaimsPaymento-payment
19WorkflowTasko-task
20WorkflowExceptiono-exception
21EvidenceDocumento-document
22EvidenceEmailThreado-email
23EvidenceAttachmento-attachment
24EvidenceEvidenceSpano-evspan
25GovernanceDecisiono-decision
26GovernanceActiono-action
27GovernanceAgentRuno-agentrun
28GovernanceAuditEvento-audit

24.3 Tool-pattern index

#PatternEffect classAnchor
1Extractionpuretp-extraction
2Lookupread-externaltp-lookup
3Validationpuretp-validation
4Classificationpuretp-classification
5Compositionpuretp-composition
6Action-stagingstagetp-action-staging
7Approval-requestcommit-lowtp-approval-request
8Aggregationread-internaltp-aggregation
9Conversion / Arithmeticpuretp-conversion
10Search / Retrievalread-internaltp-search

24.4 Action registry (kinds)

Tenant-specific actions inherit one of these kind families. The platform does not reserve names; tenants register kinds in the action registry.
FamilyExamples (illustrative)Default approval mode
create.<object>create.submission · create.claim · create.endorsementscope + policy
update.<object>.<property>update.policy.coverage · update.claim.status · update.exposure.reservescope + policy + (human gate above threshold)
commit.financial.<kind>commit.financial.payment · commit.financial.refund · commit.financial.reservequorum (typical)
state.transitionstate.claim.close · state.quote.bind · state.task.completescope + policy
communication.<direction>communication.outbound.email · communication.outbound.letterscope + content review
govern.<kind>govern.exception.resolve · govern.audit.legal_holdchain

24.5 Role × permission matrix

Default role grants. Tenants override per their authority model.
Rolepolicy.readpolicy.writeuw.reviewclaim.readclaim.writepayment.commitaction.approveaudit.read
Underwriter(within authority)(within authority)
UW Manager
Adjuster(within authority)(within authority)
Claims Manager
Reviewer(read)(scoped)
Auditor(read)
Security primary
Operator (tenant)(scoped)(scoped)
Agent (intake class)(scoped)(propose only)(scoped)(propose only)

24.6 Event taxonomy index

See §17.3 for the full taxonomy. Top-level families:
  • identity.* · policy.* · data.* · ontology.*
  • tool.* · model.* · decision.* · action.*
  • config.* · incident.* · audit.*

24.7 Integration checklist

  • Identity — SSO (SAML/OIDC) bound · SCIM provisioning · MFA required · break-glass policy signed off.
  • Tenancy — Region pin set · BYOK keys provisioned · DR class chosen · audit anchoring chosen.
  • Ingest — Channels enabled · per-channel auth configured · dedupe keys reviewed · rate budgets set.
  • Mappings — Per-source mappings authored · ontology pin set · provenance shape verified · replay sample passes.
  • Tools — Tool registry populated · scopes / markings / purposes declared · contract tests in pack.
  • Agents — Agent definitions reviewed · scopes minimised · budgets set · handoff queues provisioned.
  • Models — Approved registry populated · region pinning enforced · no-train signal verified · evals passing.
  • Action plane — SoR adapters configured · idempotency proven on contract tests · approval policies signed off · compensation paths covered.
  • Security — Markings defined · RBAC + ABAC seeded · purpose taxonomy seeded · PDP latency within SLO.
  • Observability — OTel collector configured · dashboards installed · alert routing set · cost attribution rolled up.
  • DR — RPO/RTO class verified · DR drill scheduled · backup integrity checks run.

24.8 Production rollout checklist

  • Architecture readiness — All planes deployed; contracts verified; per-plane SLOs in green for 30 days.
  • Security readiness — Penetration test cleared; SOC2 / ISO controls mapped; tenant security primary signed off.
  • Model readiness — All approved models passing eval gates; drift baselines stable; calibration up to date.
  • Integration readiness — All adapters in green; idempotency drills passed; reversal drills passed.
  • Governance readiness — Audit chain anchored; legal-hold tested; retention policy enforced.
  • Production readiness — Capacity plan signed off; on-call rotations live; runbooks current; freeze windows declared.
  • Rollout readiness — Canary plan approved; rollback rehearsed; tenant comms plan signed off.
This documentation specifies the platform contract. Concrete tenant configurations — specific models in each lane, specific tools, specific mappings, specific authority limits, specific retention durations — are tenant artefacts and live alongside this documentation under the tenant’s release governance.