ClauseClock

Calibre CC-26 · SLA interval splicer & upstream vendor apportionment

Codegeist 2026 · Apps for Business Teams

host · Next.js Web Studio · /api/clause-clock + /api/mcp

3-MinuteJudge Checklist · Codegeist 2026

0 / 7 capabilities verified in this session

  1. Seed a claim (to do)Load one of 4 canonical JSM claims — no site setup.
  2. Bend an input (to do)Flip the billing timezone or switch an interval off.
  3. Approve & commit (to do)Bind the human token to the proposal key, then write back.
  4. Watch Finance sync (to do)The @forge/realtime subscriber receives the settlement.
  5. Copy a receipt (to do)Customer, vendor or Confluence Markdown in one click.
  6. Call an MCP tool (to do)Run a Rovo MCP tool and read its JSON receipt.
  7. Reset the demo (to do)Roll the write-back back to READY for the next judge.

1-Click Seed4 canonical JSM claims · zero site setup

spreadsheet → ClauseClock

Chronograph

spreadsheetClauseClock

75mNet outagesheet 120m / 120m
99.826%Uptime10.00% tier · scale 99–100%
$1,500.00Creditof $6,000.00 cap

Caseback · proposal version key bound to the human approval token

CCLOCK-JSM-402-2026-11-NET75M-CRED150000-VEND90000

receipt
RCPT-JSM-402-2026-11-NET75M
billing clock
2026-11 · America/New_York
source
SEEDED_FIXTURE
fallback
SEEDED_SCENARIO_ACTIVE

Movement · integer-minute sweep line

5-Track Interval Waterfall

billing clock · 2026-11 · America/New_York

IRaw IncidentsΣ as reported

120m

IIMerged Union∪ overlaps folded

90m

IIIMaintenance Deduction∖ scheduled change

−15m

IVCustomer Net Outage= billable minutes

75m

VVendor Overlap Slices∩ upstream windows

45m

Naive spreadsheet

=SUM(incident durations) · no fold · no maintenance

120m → $5,000.00

99.7222% uptime · 99.00% - <99.75% (25% Service Credit)

overcharge prevented$3,500.0045m over-counted

ClauseClock

(∪ incidents ∩ billing month) ∖ ∪ maintenance

75m → $1,500.00

99.8264% uptime · 99.75% - <99.90% (10% Service Credit)

Crown · calibration inputs

Bend the evidence

Every toggle recomputes the proposal key in the browser and voids any prior human approval.

Billing timezone · contract vs UTC

Incidents · 2
Maintenance windows · 1

Audit ledger · Largest Remainder Method · integer cents

Upstream Vendor Apportionment

credit basis $1,500.00 · net 75m

PartyOverlapShareExact ¢RemainderApportioned
CloudEdge TransitVEND-CLOUD-NET · edge-bgp-us-east45m60.00%90000.00000.000000$900.00
Internal absorptionnet minutes no upstream window covers30m———$600.00
Σ vendors + internal75m$900.00 + $600.00 =$1,500.00

Proposal receipt · RCPT-JSM-402-2026-11-NET75M

One-click Markdown

Customer-facing · vendor figures withheld

▸ Preview Markdown
## SLA Service Credit Receipt · JSM-402

**Customer:** Acme Global Retail (`CUST-ACME-01`)  
**Contract:** `CTR-ACME-2026-Q4` · [governing clause](https://acme-enterprise.atlassian.net/wiki/spaces/LEGAL/pages/402001/Master+SLA+Schedule+2026)  
**Billing month:** 2026-11 (America/New_York)  
**Status:** Proposed — awaiting human-approved settlement

| Measure | Value |
| --- | ---: |
| Reported incident time (raw sum) | 120m |
| Overlapping incidents folded (union) | 90m |
| Scheduled maintenance excluded | −15m |
| **Net billable outage** | **75m** |
| Monthly uptime | 99.8264% |
| SLA credit tier | 99.75% - <99.90% (10% Service Credit) |
| Gross service credit (10.00% of $20,000.00) | $2,000.00 |
| Credits already approved this month | −$500.00 |
| **Service credit issued** | **$1,500.00** |

Reference: ClauseClock receipt `RCPT-JSM-402-2026-11-NET75M` · billing month 2026-11 (America/New_York)

Upstream vendors · overlap evidence per vendor

▸ Preview Markdown
## Upstream Vendor Recovery Claim · JSM-402

**Customer impact:** Acme Global Retail · billing month 2026-11 (America/New_York)  
**Net billable outage:** 75m · **Service credit issued to customer:** $1,500.00  
**Method:** integer-minute overlap against the net billable outage; integer cents split by the Largest Remainder Method

### CloudEdge Transit (`VEND-CLOUD-NET` · `edge-bgp-us-east`)
- Overlap with net billable outage: 45m (60.00% of the credit basis)
- Overlap windows (America/New_York): 2026-11-01 10:00 → 10:45
- **Recovery claimed: $900.00** (90000 cents)

Reference: ClauseClock receipt `RCPT-JSM-402-2026-11-NET75M` · billing month 2026-11 (America/New_York)

Finance ledger · full internal figures

▸ Preview Markdown
| Claim | Customer | Billing month | Net outage | Customer credit | Vendor recovery | Vendor split | Internal absorbed | Proposal version key | Receipt | Status |
| --- | --- | --- | ---: | ---: | ---: | --- | ---: | --- | --- | --- |
| JSM-402 | Acme Global Retail | 2026-11 (America/New_York) | 75m | $1,500.00 | $900.00 | CloudEdge Transit $900.00 | $600.00 | CCLOCK-JSM-402-2026-11-NET75M-CRED150000-VEND90000 | RCPT-JSM-402-2026-11-NET75M | READY |

Settlement write-backsplit view · two Forge surfaces, one realtime channel

Support · jira:issuePanel

JSM-402 · Acme Global Retail

75m net · $1,500.00 credit · $900.00 vendor

READY

Dry-run write-back · nothing is written until you commit

  • JSM internal noteJSM-402 · settlement receipt · vendor split · footer
  • Jira entity propertyclauseclock.settlement @ JSM-402 · status · cents · approver
  • Forge KVSsettlement::JSM-402::CCLOCK-JSM-402-2026-11-NET75M-CRED150000-VEND90000 · idempotency record
  • Cap ledgerCUST-ACME-01::2026-11 · $5,500.00 → $4,000.00 remaining
  • @forge/realtimeclause-clock-settlement-sync · publishGlobal · compact event

token · APPROVAL::CCLOCK-JSM-402-2026-11-NET75M-CRED150000-VEND90000::<approverId>

  • Enter the approver ID that signs the token.
  • Flip the human approval switch for this exact proposal key.

Finance · jira:globalPage

Portfolio ledger

@forge/realtime subscriber · clause-clock-settlement-sync

READY
listening for broadcasts…

JSM-402 has no settled receipt on this page yet. A commit from Support or from a Rovo MCP client lands here.

rovo:mcp · rovo:skill · 4 deterministic actions

Rovo MCP & SKILL.md Live Inspector

transport · Next.js Web Studio · /api/clause-clock + /api/mcp

skills/clause-clock/SKILL.md

contract aligned · manifest.yml + SKILL.md + 4 actions
---name: clause-clockdescription: Use when evaluating or settling a Jira Service Management (JSM) SLA Service Credit claim across overlapping incidents, maintenance windows, billing timezones, monthly credit caps, and upstream vendor outage feeds, or when running the ClauseClock PBT invariant audit. Do not use for single-ticket first-response SLA timers, live bank wire transfers, or unstructured PDF/Word OCR.allowed-tools:  - evaluate-clause-clock  - run-pbt-audit  - commit-credit-settlement  - reset-settlement-state--- # ClauseClock — SLA Interval Splicer & Vendor Recovery (`clause-clock`) Use this skill whenever an operator, finance controller, or SRE needs to evaluate a Jira Service Management (JSM) SLA Service Credit claim across multiple overlapping incidents, scheduled maintenance exclusions, timezone-aligned billing months, monthly credit caps, and upstream vendor outage windows. ## Mandatory Execution Discipline 1. **Zero LLM Math**: Never sum incident durations or calculate credit percentages in free-form text. Always call `evaluate-clause-clock` first to run the deterministic integer-minute sweep-line (`NetOutage = (Union(Incidents) ∩ BillingWindow) \ Union(Maintenance)`) and Largest-Remainder cent apportionment engine.2. **Contract Fee Lock**: Never pass AI-guessed `monthlyFeeCents`, `newCreditCents`, or `creditBps` overrides as authoritative values; `ClauseClock` locks monetary figures to structured contract JSON and logs any override attempt in `discardedAiAmountOverrides`.3. **Two-Phase Human Approval & Version Binding**:   - Before calling `commit-credit-settlement`, present the `proposalVersionKey` (`CCLOCK-<claimKey>-<YYYY-MM>-NET<M>M-CRED<cents>-VEND<cents>`) and ask the human approver for confirmation.   - Require an explicit `APPROVAL::<proposalVersionKey>::<approverId>` token.   - If the contract is in `DRAFT` status (`provisionalDraftMode: true`), require an explicit `financeOverrideReason`.4. **Mandatory Machine-Readable Receipt Footer**: Every response must end with the verbatim footer returned by the tool:   `[ClauseClock Receipt #<receiptId> | issue=<key> | month=<YYYY-MM> (<tz>) | mode=<LIVE|SEEDED> | netOutage=<M>m | credit=$<X> | vendorSplit=<summary>]` ## Tool Reference - `evaluate-clause-clock` (`GET`): Evaluates a seeded or live JSM claim (`hero-overlap-splicer`, `cross-timezone-boundary`, `monthly-cap-truncation`, `unapproved-contract-draft`) and returns `CalculationReceipt`, `SourceProvenanceManifest`, `approvalTokenTemplate`, and `machineReadableFooter`.- `run-pbt-audit` (`GET`): Runs `fast-check` Property-Based Testing across invariants `P1` (Bitmap Oracle Interval Equivalence), `P2` (Monotonicity & Cap Lock), `P3` (Vendor Cent Conservation), and `P4` (Idempotent Commit & Reset Round-Trip).- `commit-credit-settlement` (`CREATE`): Validates `expectedProposalVersionKey` (`409` on TOCTOU drift) and `approvalToken` (`400` on missing/invalid token or unapproved draft), atomically updates the `(customerId, billingMonth)` cap ledger, JSM internal note, Jira Entity Property, and KVS record, and publishes a `@forge/realtime` settlement event.- `reset-settlement-state` (`UPDATE`): Restores the claim and `(customerId, billingMonth)` cap ledger to `READY` so demos and audits can be re-run cleanly.

  • Evaluates a JSM SLA claim across overlapping incidents, maintenance exclusions, billing timezones, monthly credit caps, and upstream vendor outage feeds.

  • Runs fast-check Property-Based Testing across P1..P4 invariants against the Uint8Array(44640) minute bitmap oracle.

  • Commits an approved SLA credit and vendor recovery receipt after validating expectedProposalVersionKey and APPROVAL::<proposalVersionKey>::<approverId>.

  • Restores a settled claim and its monthly cap ledger balance back to the pre-settlement READY state.