Six platform primitives

Instead of single-purpose point tools, Servare models document operations as a unified set of runtime primitives.

  • Templates: Layout definitions for repeat extraction
  • Schemas: Canonical entity definitions for document data
  • Rules: Policy & jurisdiction validation constraints
  • Events: Real-time webhooks & database triggers
  • Workflows: Multi-step conditional execution paths
  • Audit Logs: Immutable provenance & change lineage
runtime-spec.yamlYAML
# Runtime Execution Spec version: "2.1" pipeline: "bank-statement-intake" trigger: type: "webhook.inbound" signature: "HMAC-SHA256" validation: schema: "CanonicalBankStatement_v1" strict_currency: true audit: immutable_provenance: true
execution-engine.jsonJSON
[14:27:01] INGEST File received: invoice_9912.pdf [14:27:02] EXTRACT Mapped 18 rows to CanonicalInvoice [14:27:02] VALIDATE Check total ($8,420.00 > $5,000.00) -> REQUIRE_APPROVAL [14:27:03] DISPATCH Slack approval alert dispatched to #finance [14:27:04] RECORD Immutable hash: 0x89f2a910...

Deterministic execution model

Servare processes every document run through five deterministic stages: Ingest → Classify → Extract → Validate → Route → Record.

Zero silent failures, built-in rate-limit retries, and complete payload visibility for every step.

Policy & jurisdiction rules engine

Configure field-level and document-level validation rules. Evaluate jurisdiction-specific requirements (e.g. state/provincial filing policy, required attachment sets) prior to committing data state.

Immutable provenance & audit logging

Every payload transformation, rule verification, and cell update is recorded with cryptographic HMAC-SHA256 signatures, ensuring complete end-to-end auditability across systems.