TARGET ARCHITECTURE / WORKING SLICE
Configuration-driven financial operations
LOCAL · EASTUS2
PF
REQUEST PATH
Control plane → bounded data-plane stamp
01Control planeTenant catalog · config registry
signed snapshot
02Tenant routerPlacement · isolation check
tenant context
03Stamp A.NET policy engine · tenant DB
outbox event
04Durable workIntegrations · reporting · audit
INTEGRATIONS / DURABLE JOB SYSTEM
Connector → mapping → checkpoint → reconcile
Versioned mappings and credential references isolate tenant configuration from connector code. Per-record checkpoints, bounded workers, retries, dead letters, and reasoned replay make failure routine and recoverable.
CONNECTIONS—governed endpoints
RECORDS ACKNOWLEDGED—— completion
RETRY WAIT—exponential jitter
DEAD LETTERS—authorized replay
| Connection / operation | Direction | Mapping | Checkpoint | Status | Next action |
|---|---|---|---|---|---|
| Load connector jobs to exercise the durable runtime. | |||||
Connection names mirror StavPay's public ecosystem; all payloads, acknowledgements, and failures are synthetic.
REPORTS / MATERIALIZED READ MODELS
Operational insight without cross-domain fan-out
Governed definitions pin domains, access roles, refresh targets, row limits, formats, and delivery. Each run produces a digested local evidence artifact over tenant-scoped read models.
CUSTOM ANALYTICS / CLOSED MATERIALIZERS
Configured spend dashboard
Loading tenant dashboard definitions…——0 writes · 0 external calls · 0 SQL
Loading governed report definitions…
REPORT RUNS—— definitions used
MATERIALIZED ROWS—bounded per export
LOCAL ARTIFACTS—digested evidence
EXTERNAL DELIVERIES0prototype safety boundary
| Report / data as of | Format | Rows | Key metrics | Evidence |
|---|---|---|---|---|
| Run a governed report to create a snapshot. | ||||
Scheduled delivery is local evidence only; production adapters would consume the same immutable report event.
STAVBOX / SAI-STYLE INTAKE
Capture → extract → trust gate → canonical invoice
Original hashes and field confidence remain immutable. Configuration controls channels, MIME/size limits, auto-accept, human review, rejection, duplicate suppression, and the authorized correction role.
DOCUMENTS—— captured
IMPORTED—canonical invoice cases
REVIEW QUEUE—confidence gated
DUPLICATE / REJECTED—fail-closed intake
| Source document | Extracted invoice | Minimum confidence | Status | Next action |
|---|---|---|---|---|
| Load the synthetic document queue. | ||||
No source document leaves the prototype; external AI calls remain zero.
OPERATIONS WORKBENCH
Invoice lifecycle
Synthetic operating records calibrated to public SEC private-fund data. Every source and assumption is labeled.
INGESTED0
→
EXCEPTIONS0
→
APPROVAL0
→
READY0
→
EXPORTED0
| Invoice | Vendor | Amount | Lines | Status | Next action |
|---|---|---|---|---|---|
| Load the portfolio to begin. | |||||
Commands are idempotent and bounded to 4 concurrent workers for this demo stamp.
STAVTASK INTEGRATION / CONFIGURED OPERATIONS
Own → review → monitor delays
StavPay work enters role queues with task-type service levels. Ownership, due dates, policy versions, and delay risk are visible without allowing task actions to bypass the source financial workflow.
OPEN—awaiting ownership
IN PROGRESS—owned work
AT RISK—75% SLA elapsed
BREACHED—manager visibility
| Work item | Queue / owner | Due | SLA | Action |
|---|---|---|---|---|
| Load the provenance-labeled work queue. | ||||
The sample is fictional and shaped by StavTask’s public ownership, approval, monitoring, and delay-reporting surface.
ACCRUALS / OFFICIAL PRODUCT SURFACE
Schedule → allocate → book → release
Frequency, invoice-match keys, adjustment authority, concurrency, and accounting mappings are tenant configuration. Periods reuse the same governed allocation engine as invoices.
CONTRACT VALUE—0 agreements
BOOKED—0 periods
RELEASED—invoice-linked reversals
HELD REMAINDER—fail-closed review queue
Load schedules to generate the monthly accrual timeline.
| Agreement | Vendor / category | Contract | Periods | Reconciliation | Action |
|---|---|---|---|---|---|
| Load the accrual scenario. | |||||
Schedule generation uses exact residual handling; every accounting posting must balance before commit.
SERVICES / OFFICIAL PRODUCT SURFACE
Vendor → contract → SKU → assignment
A shared catalog resolves service usage into allocation eligibility by invoice date, replacing embedded customer-specific entitlements.
APPROVED VENDORS—governed master records
ACTIVE CONTRACTS—— committed
SERVICE SKUs—vendor + region + contract
ASSIGNMENTS—user · group · entity
Load the catalog to evaluate contract dates.
| SKU / service | Vendor / contract | Region / unit | Unit price | Effective usage | Evidence |
|---|---|---|---|---|---|
| Load the service catalog. | |||||
Bulk imports are bounded and idempotent; retroactive edits require controller authority and a reason.
LEGAL / OFFICIAL PRODUCT SURFACE
Matter → rate review → allocation
Effective matter scope, budgets, timekeeper rates, billing formats, and override authority are configuration—not customer-specific code.
ACTIVE MATTERS—— budget
RATE CARDS—effective timekeeper terms
LEGAL SPEND—— invoices
EXCEPTIONS—line-level review evidence
Load matters and legal invoices.
| Invoice | Matter | Format / lines | Amount | Review | Action |
|---|---|---|---|---|---|
| Load the legal scenario. | |||||
Compliant lines become canonical invoices; exceptions remain held until an authorized, reasoned override.
1099 / OFFICIAL PRODUCT SURFACE
Eligibility → review → filing package
Configured tax classifications and category rules select reportable spend; supporting invoice allocations remain attached at line level.
ELIGIBLE FORMS—1099-NEC drafts
REPORTABLE—configuration-derived
SUPPORT—— allocation legs
EXTERNAL SENDS0prototype safety boundary
| Payee | Form / tax year | Reportable | Support | Status | Next action |
|---|---|---|---|---|---|
| Generate forms from reviewed invoice allocations. | |||||
Identifiers are masked. Filing and delivery create local evidence packages only.
CHARGE BACK / OFFICIAL PRODUCT SURFACE
Allocation → receivable → settlement
Inter-entity balances are derived from exported allocation legs, netted by configured dimensions, and packaged with source-invoice support.
CHARGE BACKS—benefiting entities
OPEN RECEIVABLE—due to paying entity
SETTLED—simulated intercompany
SUPPORT—source allocation legs
| Internal invoice | Due from / due to | Amount | Support | Status | Next action |
|---|---|---|---|---|---|
| Generate from exported allocations. | |||||
Settlement is simulated locally; balanced due-to/from postings and audit evidence are durable.
TIME TRACKING / OFFICIAL PRODUCT SURFACE
Task entry → compliance → allocation driver
Task templates, required hours, approval authority, missing-time behavior, and driver dimensions are tenant configuration. Approved time becomes a versioned allocation input.
TIMESHEETS—weekly records
RECORDED HOURS—governed task entries
MISSING HOURS—warning workflow
DRIVER SNAPSHOTS—immutable on approval
| Employee / week | Department | Hours | Compliance | Status | Next action |
|---|---|---|---|---|---|
| Load the realistic weekly time scenario. | |||||
Missing time follows configured warning policy; employees cannot approve their own sheets.
PROCUREMENT / OFFICIAL PRODUCT SURFACE
Requisition → PO → receipt → match
The official goods/services catalog, pricing, delivery profiles, tax jurisdiction, adjustments, approval tiers, PO numbering, receipt requirements, and three-way tolerance are governed tenant configuration.
MASTER INVENTORY CATALOG
Goods & services under one control plane
DELIVERY PROFILES—
PRICE VARIANCE—
NYC PUBLIC REFERENCE—
EXTERNAL LOOKUPS0
REQUISITIONS0
→
APPROVAL0
→
PO / RECEIPT0
→
MATCHED0
| Requisition | Vendor / category | Amount | Approvals | Status | Next action |
|---|---|---|---|---|---|
| Load the procurement scenario. | |||||
Matched invoices enter the same durable allocation and accounting workflow.
BUSINESS ONBOARDING / PAYMENTS + STAVCARD
Identity → bank ownership → KYB → eligibility
One configuration-driven eligibility boundary governs Payments and StavCard. Required checks, ownership threshold, roles, product actions, and annual review behavior are policy—not tenant code.
LEGAL ENTITYNot startedlegacy configured status
CASE STATUSLEGACYmigration fallback explicit
BANK OWNERSHIP0 / 0masked references only
KYB CONTROLS0 / 6clear / required
MASKED IDENTITY
Entity & beneficial owners
Open the fictional scenario to create a durable onboarding case.
CONFIGURED CONTROLS
Verification evidence
Existing tenants remain on an explicit legacy status until a case opens; an open incomplete case fails closed for new payment submission and card issuance.
ENTITY REGISTRY / STAVORG → STAVPAY BRIDGE
Canonical funds, ownership & financial visibility
Effective-dated legal-entity data resolves sparse transaction snapshots before allocations, budgets, payments, and cards. Vocabularies, bounds, conflict behavior, and bank visibility are configuration—not customer code.
LEGAL ENTITIES0registry not loaded
RELATIONSHIPS0bounded ownership graph
SIGNATORIES0effective authority
BANK VISIBILITY0masked synthetic balances
DEADLINES0upcoming compliance
CHANGE REQUESTS0maker-checker lifecycle
Load the fictional structure to create a durable canonical registry.
No governed entity changes.
Unknown or kind-conflicting entities fail closed for review; no unmasked account or live balance data is stored.
STAVCARD / INFERRED PRODUCT CONCEPT
Issue → authorize → capture → settle
Governed virtual/physical issuance, a standalone authorization boundary, allocation-ready capture, and exact settlement evidence—not represented as an existing released product.
PROGRAM CARDS0physical + virtual
AUTHORIZED SPEND$0authorized + cleared
DECLINES0policy enforced at authorization
RECEIPT EXCEPTIONS0threshold is configuration
T&E RECEIPT COMPLIANCE
Evidence → match → reminders → authorization control
REQUIRED0non-declined transactions
COMPLETE0exact financial match
PAST DUE0demo as of Aug 22
RESTRICTED CARDS0authorization decision input
Load card activity to evaluate configured receipt deadlines.
Load the scenario to issue demo cards.
AUTHORIZATION DEFAULT—
SETTLEMENT—
COUNTRIES—
BLOCKED MCCs—
SETTLED VOLUME—
ILLUSTRATIVE NET REVENUE—
| Card / time | Merchant | MCC mapping | Amount | Decision | Action |
|---|---|---|---|---|---|
| No card authorizations have been evaluated. | |||||
Authorization, capture, settlement matching, and illustrative program economics all pin the active configuration; no network or processor is called.
STAVCARD OPERATIONS
Disputes & reimbursements
DISPUTES—— disputed
OPEN CASES—evidence workflow
REIMBURSEMENTS—— submitted
EXTERNAL ACTIONS0prototype safety boundary
| Dispute | Status | Action |
|---|---|---|
| Load card operations. | ||
| Reimbursement | Approvals | Action |
|---|---|---|
| Load reimbursements. | ||
KYB, dispute evidence, approval tiers, and external-action modes are tenant policy.
VENDOR MASTER / PAYMENT CONTROL
Identity, evidence & bank-change governance
Tax evidence, sanctions status, independent activation approvals, out-of-band bank verification, and a configured cooling-off period determine payment eligibility. A pending bank change fails closed at submission.
GOVERNED VENDORS—— active
ONBOARDING—tax · sanctions · approvals
BANK CHANGES—— pending
PAYMENT BLOCKED—fail-closed beneficiaries
| Vendor identity | Tax / screening | Payment terms | Bank reference | Status | Next action |
|---|---|---|---|---|---|
| Load the governed vendor scenario. | |||||
BANK-DETAIL CHANGE CASES
Out-of-band verification → controller approval → cooling off
| Case / vendor | Requested change | Evidence | Approvals | Status | Next action |
|---|---|---|---|---|---|
| No bank-change cases loaded. | |||||
All vendor and bank values are synthetic and masked; the workflow makes no external verification or payment calls.
PAYMENT CENTER / OFFICIAL PRODUCT SURFACE
Multi-rail payment operations
Configuration selects rail, funding account, approval policy, provider route, failover, and reconciliation tolerance.
RAIL + TREASURY INTELLIGENCE
Checks · ACH · RTP · FedNow · wire · FX
Evaluating configured rail, compliance, provider, funding, and FX policy…
No bank-account configuration is available.
REAL-TIME FINANCIAL VISIBILITY / OFFICIAL PRODUCT SURFACE
Balances → statements → explainable reconciliation
FRESH ACCOUNTS015 minute policy
STATEMENT ENTRIES0bounded idempotent ingestion
EXACT MATCHES00 StavCard settlements
EXCEPTIONS0review + unmatched
Ingest the fictional masked feed to replace estimates with dated balance snapshots.
| Statement entry | Account / category | Direction / amount | Reconciliation | Linked record |
|---|---|---|---|---|
| No statement entries ingested. | ||||
All balances, statement entries, and references are fictional and masked. Provider authentication and encrypted raw-feed retention remain production boundaries.
PENDING APPROVAL0
→
READY0
→
IN FLIGHT0
→
RECONCILED0
| Payment | Beneficiary | Rail / route | Amount | Status | Next action |
|---|---|---|---|---|---|
| Build a payment batch from accounting exports. | |||||
Payments remain idempotent by source invoice and require independent maker-checker approval.
BUDGET / OFFICIAL PRODUCT SURFACE
Allocation-aware budget control
Actuals are rolled up from immutable allocation legs into configured grid-code and expense-category dimensions.
ANNUAL BUDGET—FY —
ALLOCATED ACTUAL—— source cases
REMAINING—— mapped legs
UTILIZATION—warning threshold 80%
CONFIGURED HIERARCHY
BOUNDED DRILL-DOWN
Select a hierarchy node to inspect its generated budget codes.
All allocated spend resolves to a configured budget grid.
CONTROL PLANE
Configuration lifecycle
A draft cannot affect financial decisions until it validates and receives maker-checker approval.
Ready to validate the draft against the closed policy schema.
INVOICE APPROVAL ROUTING
Preview a tenant rule without creating a transaction
Loading configured route…
DATA PLANE / STAMP A
Allocation simulator
INVOICETMD-Q1-26-8802Tessellate Market Data · Q1 2026
AMOUNT$1,240,000.00Market data / active entitlements
Selected policy
Service & User / Headcount
amount × entity headcount ÷ eligible headcount
The result will record its policy and metric snapshot.
MAKER / CHECKER
Approval queue
No invoices are awaiting approval.
ACCOUNTING INTEGRATION
Balanced exports
No accounting exports are queued.
AUDIT INTEGRITY / TENANT EVIDENCE
Deterministic state manifest
Each governed domain is stably ordered and canonically hashed into one tenant state root. The prototype performs no external write; production signs the root and retains canonical evidence in object-lock/WORM storage.
STATE ROOT—SHA-256
DOMAINS—independent digests
RECORDS—tenant-scoped
EXTERNAL WRITES—local evidence only
Loading tenant evidence manifest…
Hashing proves content integrity, not signer identity. A production signature boundary is explicitly modeled.
ASYNC BOUNDARY
Transactional outbox
Run an allocation to produce an AllocationCalculated event.
PUBLIC DATA / PROVENANCE
SEC private-fund benchmarks
PRIVATE FUNDS—2025Q3 Form PF
GROSS ASSETS—aggregate, USD
NET ASSETS—aggregate, USD
ADVISER SAMPLE—public Form ADV rows
2025Q3 BY FUND TYPE · OFFICIAL AGGREGATESGAV / NAV independently rounded to USD billions
PUBLIC FORM ADV ADVISER SAMPLEseparate public records
Form PF figures are anonymized aggregates, rounded and/or masked; they identify no adviser or private fund. Adviser facts are public self-reported Form ADV data. No public record is mixed into fictional tenant transactions.
OFFICIAL SEC REFERENCE DATA / 2010–2026
Registered fund & share-class catalog
Real public identifiers are searchable as master-data candidates; they remain isolated from fictional customers, invoices, and allocations.
CLASS RECORDS—full 2026 file
UNIQUE SERIES—SEC series IDs
REGISTRANTS—unique CIKs
| Ticker | Series / class | Registrant | SEC identifiers | Public filing |
|---|---|---|---|---|
| Loading public reference records… | ||||
ILLUSTRATIVE / ZERO WRITE
Allocate by official reported net assets
VOO, SPY, and QQQ are unrelated public references—not customers or a real expense relationship. This proves the dated metric and exact rounding path without presenting synthetic NAV as real.
Loading reference allocation…
Public reference data is loading.