FoldSense distinguishes code presence, configuration, live execution, generated artifacts, manual device acceptance, provider payment/budget blocks, and cryptographic custody. Those states are not interchangeable.
Lifecycle state: FROZEN / CLOSED OUT. Active feature development is paused. Work resumes only after explicit operator direction tied to a new project or renewed interest.
The signed media capture and the later local five-protein run are separate time-scoped evidence objects. Provider changes observed later do not rewrite the signed snapshot or become production provider PASS evidence.
The later local run reported receipt SHA-256 54dbd823df89e6329c8a405fcff5a656b5a26b2e51a53007a730b771527451b7 and pyPept receipt SHA-256 9d8ca92bdfff6506dffe3cae32f1b4320abec0e46953c3e7bb9a10679ed1446a. The exact receipt bytes are not present in Git at closeout, so these are retained as local hash-only observations, not signed or Git-custodied receipt artifacts.
Each protein record contains BILN, a text figure, evidence query, source list, and a six-line prebuilt conversation.
The pinned pyPept generator produces one generated fragment conformer for each demo and records exact input/output hashes. The claim ceiling is:
GENERATED_CONFORMER_NOT_EXPERIMENTAL_STRUCTURE_NOT_MD
The five-protein acceptance imported the existing canonical artifacts only after verifying their manifest relationships. PDB and HTML artifacts passed for all five proteins, with artifact-verification receipt SHA-256 9d8ca92bdfff6506dffe3cae32f1b4320abec0e46953c3e7bb9a10679ed1446a.
This establishes a local governed pyPept artifact PASS. Publication of the generated structure set into production remains a separate release action and is not implied by the local verification.
| Backend | Implemented route | Observed state | Judge interpretation |
|---|---|---|---|
| Vapi | /api/vapi-status | 5/5 PASS | Configured assistant/readback path works. Actual browser call + reader tool action remains a manual device gate. |
| ElevenLabs realtime | /api/elevenlabs-token | 5/5 PASS | Single-use realtime Scribe token issuance works independently from paid TTS. |
| ElevenLabs speech | /api/elevenlabs-event-tts | Historical five-protein receipt: FAIL · HTTP 401 Follow-up: provider payment block confirmed | Account auth, realtime token and voice metadata each returned 200; minimal TTS returned payment_issue / payment_required. This is not a FoldSense authentication, voice-ID or molecular-state defect. Successor harness classifies it as EXPECTED_PROVIDER_PAYMENT_BLOCK. |
| Exa | /api/exa-search | 5/5 PASS | External evidence retrieval succeeded; retrieval cannot rewrite the frozen molecular event. |
| Apify | /api/apify-status, /api/apify-ingest | 5/5 PASS | Actor start and completed dataset collection succeeded and remain distinct from retrieval/synthesis. |
| GMI Cloud status | /api/gmi-status | 5/5 PASS | Authentication/model discovery works; status is not inference proof. |
| GMI Cloud inference | /api/gmi-interpret | EXPECTED_BUDGET_BLOCK | GMI_CALLS_DISABLED_BY_BUDGET_GATE · HTTP 409 is the expected safety result while the USD 10 paid-call gate remains closed. |
| Gemini + Exa | /api/gemini-exa | NOT_CONFIGURED_OR_NOT_LOCKEDGEMINI_NOT_CONFIGURED · HTTP 503 | The direct Gemini route is independent from GMI-hosted Gemini. No direct Gemini success is claimed. |
| Integrated | Five-protein E2E harness | Historical receipt: RECORDED_FAILURES | The historical classifier treated the ElevenLabs payment response as generic FAIL. The receipt is preserved. A successor rerun is required before PASS_OR_EXPLICIT_BLOCKS may be claimed. |
Judge rule: PASS, controlled budget block, confirmed provider payment block, unconfigured optional route, and hard implementation failure are intentionally different states. See Judge status for the exact cause table and rejected screenshot evidence.
The six scripted turns per protein can be rendered once through the locked ElevenLabs event-TTS route and stored under /audio/<protein>/line-XX. The generator emits hashes and does not print secrets.
Until provider TTS billing is restored and those media files are generated, reviewed and published, the Molecular Reader retains browser/native speech and text/ARIA fallback.
Generating all five conversations can require up to 30 TTS calls and therefore remains an explicit GUM opt-in. The currently confirmed provider payment block prevents those paid renders from being claimed as available.
FOLDSENSE_SYMPHONY_V1 is deterministic molecular sonification. Speech/TTS narrates an event; sonification maps molecular tokens/context into sound. A speech-provider payment block does not remove deterministic sonification, and vice versa.
The E2E walkthrough keeps those channels distinct so a single “audio” status cannot hide which path passed, failed or was provider-blocked.
Checking for a published receipt…
Checking for a published integrated screenshot…
SHA-256 establishes byte identity. Minisign/Ed25519 establishes an actual detached cryptographic signature only when signing and verification occurred. A hash is not a signature. Merkle/MMR remains NOT_COMMITTED unless an explicit commitment operation is performed.
Screenshots, audio and videos are projection/media artifacts. Their signatures prove exact bytes; they do not independently prove scientific correctness. The first five protein screenshots were signed but later rejected as protein-specific evidence because all five were byte-identical; successor capture code now hard-gates protein render identity and distinct hashes before signing.