math.sequences

Three distinct suites: educational examples on the calculator page, this legacy regression count (12/12 golden + boundary), and the CVP verification suite below. They are not the same number. Property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the CVP Manifest . SKIP (0/0) means that suite has no published vectors.

STALE · Build schema 1.0.3 matches page · production binding STALE · Semantic contract ✓ · Last attestation PASS · current evidence changed · re-attestation required · CVP STALE · attestation STALE — Production CURRENT withheld · Public/cache ✓ · Origin ✓

CVP verification suite

Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Verification revision 2026-09-22.discrete-algebra-cvp. Calculation version 1.0.0. CVP 1.0.0-proposed. 5/5 golden · 3/3 CVP boundary · 6/6 invalid · 3/3 property · 4/4 cross-interface · 1/1 cross-calculator · 6/6 CVP contract. digest fe9aed69431a.

• Golden (oracle-backed) 5 / 5
• CVP boundary 3 / 3
• Invalid input 6 / 6
• Property 3 / 3
• Cross-interface 4 / 4
• Cross-calculator 1 / 1
• CVP contract 6 / 6
• Interfaces PASS · UI (SSR) / REST / MCP
• Interface claim ui-ssr is query-result HTML, not a live browser session. Error-path engine·REST·MCP 1/1 (status, code, calculation_version). SSR compared on URL-canonical requested calculations; empty query is idle (not an error) and JSON-typed object/array inputs are REST/MCP-only.
• Verified scope all published modes
• Assurance Core

• release artifacts aligned PASS
• schema output required declared PASS
• schema valid input executes PASS
• engine success output validates schema PASS
• schema rejects incomplete input PASS
• rest success payload validates schema PASS

Fingerprint sha256:ac633fb6a40d747074c2c45a941fe716881af18188b8106d6e4ae77635cbed0e

Input schema sha256:f4bec45ebd1ac51417827dbf207258b1f2ccd72527597c58159b524c703e14a7 · Output schema sha256:01c274ed03ed17ad714cbc73df6bebd2b0870b9cfd46b35fac7435fc90e62232 · Build-time SHA-256 digests prove published artifacts agree with each other (release_integrity.scope=workspace). Production attestation GETs canonical URLs twice (public/cached view and origin), including Capability HTML, via npm run attest:production --write (published at /.well-known/calculatorx-production-attestation.json) and fails if the public Capability page advertises a different calculation_version. This is artifact consistency, not an independent immutable release log.

Tool

sequence

Engine

sequence

Engine build

2026-09-22

Evidence core

2026-09-22T02:47:11.470Z

Rendered

2026-10-06T23:48:35.507Z

Last reviewed

—

Assumptions

• The Result Card includes an engine-linked stem figure of a_k (marker is published term; at most 16 indices, window ending at n). Same closed form / recurrence as REST/MCP. Terms array is not a REST field. Huge BigInt terms omit the figure.
• Integers
• n ≤ 1000
• Not Pascal / partition / n!

Limitations

• Not Pascal’s triangle and not integer partition
• Not /calc/math/factorial and not /calc/math/permutation-combination
• Integers only — no Binet float Fibonacci
• Engine id is sequence; never alias the add/sub engine id arithmetic
• n=0 on AP/GP → VALUE_MUST_BE_POSITIVE
• n>1000 → VALUE_ABOVE_MAX
• unknown mode → INVALID_MODE