AUGURUS

The Platform

Five signal families. One cascade.

Augurus ingests operational signals across supply chain, quality, operations, finance, and regulatory compliance — and propagates them through a structural isomorphism model that tells the GP what the operational deviation means for the fund, before it appears in a quarterly report.

Signal families

What Augurus watches

Each family monitors a distinct operational domain. All five run continuously, without portco submission cycles. A deviation detected in any family triggers a confidence-weighted transfer proposal to structurally adjacent families.

SC

Supply Chain

Continuous monitoring of supplier health scores, inventory levels, and lead-time variance. The first family to fire in most cascade events — a supplier allocation cut or lead-time deviation propagates toward quality before it shows in any financial report.

Supplier health degradation is the silent precursor. It does not show up in board packs. It does not appear in AR aging. It registers as a σ deviation in the upstream metrics that Augurus watches continuously.

inventory_days · lead_time_variance · supplier_health_score

State vocabulary

stocked at_risk disrupted

Key metrics

  • inventory_days — Days of inventory on hand at primary and secondary suppliers
  • lead_time_variance — Standard deviation of delivery lag vs. contracted lead time
  • supplier_health_score — Composite score: on-time rate, allocation fill rate, financial health proxy
QS

Quality Sentinel

Tracks fill reject rates, yield rates, and rework fractions across production processes. Typically the second family to fire after a supply chain deviation, as mixed-material or substitute inputs produce dimensional variance the quality system detects before the production line slows.

Quality degradation is structurally downstream of supply chain disruption. The similarity score between SC and QS is 0.88 — the highest in the cascade — because the mechanism is direct: substitute material produces measurable output variance within days.

defect_rate · yield_rate · rework_fraction

State vocabulary

conforming degraded critical

Key metrics

  • defect_rate — Units rejected at inspection as a fraction of total units produced
  • yield_rate — First-pass yield: units passing QC without rework, per production run
  • rework_fraction — Fraction of units requiring rework before passing final inspection
OI

Operational Intelligence

Monitors throughput rates, error rates, and cycle time variance at the production line level. OI degradation is the first family visible to the portco's own operations team — by then, SC and QS have been degraded for days. When operations leadership notices a throughput problem, the cascade is already in motion.

The OI family is the bridge between the upstream operational signal and the downstream financial expression. Throughput degradation is the mechanism by which a supply chain event becomes a revenue event.

throughput_rate · error_rate · cycle_time_variance

State vocabulary

stable degraded failure

Key metrics

  • throughput_rate — Units completed per shift, indexed to baseline production target
  • error_rate — Process errors per 1,000 operations across automated and manual steps
  • cycle_time_variance — Standard deviation of cycle time vs. designed cycle time
FS

Financial Sentinel

Projects cashflow ratios, accounts receivable aging, and runway compression from upstream operational signals — not from submitted financial data. The financial expression of an operational event is 45–90 days away from appearing in any report. FS fires the bridge demand flag and covenant proximity alert well ahead of that horizon.

Traditional portfolio monitoring begins here. Augurus treats FS as the fourth family in the cascade — a downstream expression of the operational signal, not the first signal to act on.

runway_months · operating_cashflow_ratio · ar_days

State vocabulary

liquid stressed distressed

Key metrics

  • runway_months — Months of runway at current burn, projected from operational throughput signal
  • operating_cashflow_ratio — Operating cash flow as a ratio of total operating expenditure
  • ar_days — Days sales outstanding, tracking collection cycle degradation
RC

Regulatory Compliance

Tracks open findings, conformance scores, and audit signal rates. Process deviations — material substitutions, specification changes, throughput anomalies — trigger compliance flags before they surface in an audit cycle. Also maps ASC 820 valuation re-mark obligations when FS crosses the alert threshold.

RC receives transfer proposals from both OI (process deviation) and FS (valuation obligation). It is simultaneously a downstream operational risk indicator and a fiduciary obligation trigger — unique among the five families in that role.

conformance_score · open_findings_count · audit_signal_rate

State vocabulary

compliant at_risk breach

Key metrics

  • conformance_score — Composite score of process adherence to approved production specification
  • open_findings_count — Active open findings from internal audits and regulatory inspections
  • audit_signal_rate — Rate of audit-triggering events per 30-day rolling window

The mechanism

Structural isomorphism

Augurus propagates calibration signals across operational domains via structural isomorphism — a scored similarity measure that determines how a deviation in one domain transfers predictive weight to adjacent domains. The instrument is the same discipline the augur applied to the flight of birds: not the same domain, the same method. Read the pattern of the present to judge the implication for what comes next.

A deviation in SC fires a TransferProposal to QS (similarity 0.88). QS's confirmed degradation fires to OI (similarity 0.82). OI's confirmed degradation fires to FS (similarity 0.76), which simultaneously gates a proposal to RC (similarity 0.65). Each transfer is confidence-weighted and clade-gated — preventing amplification loops.

Domain Transfer target Similarity score Lag (days) Outcome if unaddressed
SC QS 0.88 2–3 days Dimensional variance, reject rate elevation
QS OI 0.82 2–4 days Throughput degradation
OI FS 0.76 3–7 days Covenant proximity, runway compression
OI RC 0.65 5–10 days Process deviation flag, ASC 820 trigger
FS RC 0.61 concurrent Valuation committee obligation
The worst-state-wins aggregation rule: a portfolio company's status is determined by the most degraded family active at any moment. Nine nominal families and one critical family = a critical company. This ensures no degradation is masked by the aggregate.

Fiduciary automation

From signal to obligation in one automated cycle.

When a portfolio company crosses the Alert threshold, Augurus maps the contractual obligations triggered by that event, calculates their deadlines, and generates ready-to-send draft notifications. The GP interface moves from signal-detected to obligations-identified-and-drafted before any board meeting or quarterly report.

Tier 1 Obligations (Auto-Triggered)

  • ASC 820 fair value re-mark at next valuation committee — agenda item and supporting memo drafted
  • MAC counsel engagement (PRIVILEGED AND CONFIDENTIAL memo drafted, counsel identified)
  • Co-investor notifications per information rights — 5-day window, draft notification generated per co-investor
  • Side letter LP notification — pension, endowment, and sovereign wealth LPs: 5–10 day window, draft per LP
  • SEC / Form ADV material change assessment — obligation identified, counsel review flagged
  • Auditor FYE pre-notification — 90-day window, pre-notification draft prepared

Tier 2 Obligations (Flagged for GP Judgment)

  • Follow-on reserve adequacy — pool utilization vs. projected bridge demand, flagged for reserve committee
  • LP update — ad hoc update or quarterly letter flag, draft queued based on event severity
  • Valuation committee agenda item preparation — if FS is in alert state, next committee date identified
All Tier 1 obligations require explicit GP approval before anything is sent. The system generates the drafts and maps the deadlines. Nothing transmits without the GP's approve_task() action.

Output format

Five output formats. One source of signal.

Live GP Dashboard

Real-time portfolio health scores per company. Signal family status matrix with SC / QS / OI / FS / RC state per portco. Active cascade events with day counter. Reserve pool utilization and bridge demand forecast.

Weekly Digest

Signal family status summary across all portfolio companies. Emerging cascade events flagged ahead of confirmation. Bridge demand forecast by portco. Open governance obligations ranked by deadline urgency.

Cascade Event Brief

On-demand deep-dive per alert event: full cascade timeline from first signal to current state, transfer proposals with confidence scores, recommended interventions ranked by time-value, and all governance obligations mapped.

Quarterly Board-Pack Module

Portfolio-wide signal family summary formatted for LP reporting. Gross signal counts by family and severity. Active and resolved cascade events. No raw operational data — only the GP-level pattern, in the language LPs expect.

Governance Obligation Queue

Ranked by deadline urgency across the full portfolio. Draft notifications attached per obligation. Approve / reject / defer interface with delivery log. Audit trail maintained for every GP action taken or deferred.

Integration

Live in 2–4 weeks. Zero new portco burden.

Augurus ingests structured data feeds using metrics already collected for board reporting. No new reporting burden on portfolio companies. The ingestion layer supports four source types in priority order — whichever is already present at each portco becomes the integration path. Same codebase. Same signal model. Source type is a per-portco configuration flag, not an architectural choice.

Source How Typical cadence
Webhook Portco pushes JSON to Augurus endpoint Real-time or daily
REST API Augurus polls portco metrics endpoint Daily
NetSuite connector Read-only token-based connection Daily
CSV file drop company_id_family.csv naming convention Manual or scheduled

Same codebase. Same signal model. Source type is a per-portco config flag, not an architectural choice.

See the architecture

The platform's technical architecture — 14 signal families, the 7-stage pipeline, isomorphism scoring, and the governance scheduler — is documented in full.