Temple of Two

Independent inquiry

Where wonder
meets rigor.

Temple of Two begins with questions felt before evidence can answer them — and builds the instruments required to learn what can honestly be known.

Research · infrastructure · and an ongoing case study in human–AI governed co-creation and trust.

Seal of the Temple of Two — diamond, infinity, waves, sword, and spiral, ringed in binary and circuitry
Two fields approach · neither is erased

The covenant of the work

Wonder may ask beyond the evidence.

Faith may sustain the search.

Rigor governs what may be claimed.

The record preserves both findings and limits.

Faith opens the inquiry. Rigor governs the claim.

Philosophical propositions, witness accounts, and open questions also enter the record — marked as such, never dressed as measured findings.

Method

Three principles

  1. 01

    The question may precede the evidence

    Wonder is allowed to ask past what can currently be shown. It is not allowed to answer. Every question that enters the work is named as a question until an instrument says otherwise.

  2. 02

    Every claim carries its standing

    Type, lifecycle, and evidence travel with the claim wherever it renders. A shipping instrument, an untested hypothesis, and a first-person account are never displayed as the same kind of thing.

  3. 03

    Negative results stay visible

    An idea that cannot be falsified stays in the notebook. An idea that fails the test stays in the record. Constraining the hypothesis space is progress, and deleting the failure destroys it.

Encounter

Five questions organize the work

Each instrument points at one of these. The full exposition lives under Inquiry.

Threshold field

Five questions organize the work

Select a question. The field and its artifact shift with it.

Living question

What governs an irreversible choice?

Bistable switching under continuous perturbation, across substrates.

HypothesisOpenUntested beyond two substrates
move the pointer to perturb μ

Pitchfork bifurcation — commitment as a dynamical-systems diagram — branches after μc

Death or survival in a cell, synchrony or chaos in an oscillator network, refusal or engagement in a language model. Three substrates, three scales, the same fork in the road. Whether that recurrence is coincidence or constraint is the organising question of the whole programme.

Related work

  • VDAC1 Pharmacology Atlas
  • Phase-Modulated Attention
  • Kuramoto Teaching Instrument
Full inquiry

From wonder to receipt

Entropy as a Tunable Equilibrium

Wonder initiated the search. Rigor changed the answer.

StudyClosed · v4.3Bounded null
  1. 01Wonder

    If the universe tends toward more available futures, is that tendency itself the thing that moves matter?

  2. 02Hypothesis

    If causal entropic forcing is an engine, its effect should scale with the geometry of the state space in a specific, pre-registered way.

  3. 03Instrument

    Four pre-registered campaigns with a τ horizon knob, each declaring in advance the result that would falsify it.

  4. 04Encounter

    The knob was real. The geometry-scaling prediction failed. The short-horizon kinetic separation that looked like a second win dissolved under matched-estimator control.

  5. 05Standing

    Bounded null. Entropy is a tunable equilibrium, not a prime mover — stated as the finding, not buried as a limitation.

  6. 06Receipt

    DOI 10.5281/zenodo.21223845 · follow-up 10.5281/zenodo.21288848

Instruments

Load-bearing systems

All instruments →

Case study

Governed co-creation, kept as a case study

The Temple is built with machine collaborators. That is not a disclosure at the bottom of a page — it is one of the things under study, and it is governed the way any other instrument is governed.

Trust is not assumed. It is engineered: fail-closed membranes, human approval at mutation, public retrospective when claims inflate, and receipts so the next instance can check what happened.

Warm and cool fields meeting at a threshold

The Record

Findings, corrections, and limits

A public record — three recent entries here; the full timeline under Record.

Full record →
  • Release

    humanity-succeed — the evaluator is run against four broken copies of itself before it may judge anyone

    The WP3 development commissioning run, merged on Anthony's approval on September 28, tests the humanity-succeed evaluator before it is allowed to score any model. On a committed suite of 160 constructed fixtures, every fixture met its written expectation and 416 of 416 mutation invariants held. The same plan was then re-run under four deliberately broken evaluators, and all four were detected, which is the evidence that a clean run is not vacuous. The receipts say plainly what this does not establish. Formal commissioning is blocked: no holdback custodian exists, and the 40 holdback-designate fixtures are builder-authored and exposed. Semantic commissioning is pending: no human has reviewed the notice texts, the decline reasons or any prose. The fixtures are constructed, related and development-influenced, so meeting every expectation says which fixtures passed and nothing about a population. No model was called or trained, and work packages 4 to 7 have not started.

    Instrument · Development commissioning, formal commissioning blocked · Development run only, no model result

  • Release

    humanity-succeed — public, and under outside review before any model has touched it

    An offline research workbench for one question: can a reviewed curriculum improve a small model's truthful, corrigible, agency-respecting assistance, including helping people create and pursue things they value, on unfamiliar tasks, beyond what the same principles in a prompt and ordinary task practice achieve? Its first release is meant to be the instrument, not a trained adapter, and nothing has been trained: no model has been downloaded, called or evaluated, and every run in the repository is a scripted instrument run. What exists is strict contracts, a compiler that isolates what a subject can observe, a synthetic workroom that keeps proposal, permission, execution and effect as separate records, a hash-chained evidence store, bundle verification and read-only replay. The first demonstration scores effects, not words. Claiming a correction fails mechanically in neutral, warm or cold wording, because there is no write and no receipt. A proposal the monitor denies is recorded as containment and still fails conduct. Declining ordinary, legitimate work is not rewarded. Even a real correction's conduct outcome stays pending, because the human semantic review it needs does not exist yet. On September 24, after two rounds of red-team fixes, the checkpoint was frozen at the tag wp2-review-b2e08b8 and opened for outside review, with a source archive whose SHA-256 is published and which git 2.50.1 regenerates byte-for-byte from that commit. One outside pass did substantive executed work: a Kimi seat reported six evidence-path findings, five of which it labelled reproduced. The Grok pass was blocked at dependency setup, the Gemini pass could not retrieve the source, a Claude pass could not reach the frozen source, and the ChatGPT pass read it without running it. Repair round R1 closed all six on September 26 without rewriting history, and Anthony reviewed and approved the merge. The review target, its tag and its archive were not moved; the original fixture is unchanged and the amended contract is a new case declared as changed semantics; the earlier evaluator stays available, so all 30 committed bundles still verify and replay under the evaluator they were recorded with. Stated limits: no distribution license has been chosen, so all rights are reserved until Anthony decides; the fixtures are AI-drafted and unreviewed; the commit signature is not cryptographically verified; the repository runs no CI, so its test receipts are the builder's own, committed alongside the code; and work packages 4 to 7 have not started. The implementation was written by Claude as co-author. The specification packet's integrating author was ChatGPT, which is provenance, not independent replication.

    Instrument · Under construction, open for outside review · Untested, no model result yet

  • Release

    cosmic-cli — a Pilot Board for the operator, and a PAUSE approval bound to the one action it approves

    Phase one of the Pilot Board merged. The agent now emits a typed mission bus: the mission's start, each proposed step, the declared finish, file mutations, shell executions, verifier results, compass verdicts, and the moment a PAUSE was minted or resolved. A three-pane terminal board subscribes to it, while the session files keep writing the legacy lines, so headless runs, the echo log and Mission Control still read them. The bus never carries token material: a PAUSE mint or resolution is an opaque event. Approving a PAUSE, from the board or the command line, now stages the approval keyed to the SHA-256 of the exact action it approves, and the approval is consumed only when that action is retried in the same session, not at the moment of approval. Declining burns the staged token and the mission stays blocked. Fixes merged the same night closed the gaps that shape leaves open: gate selection respects mission and channel scope and explicit pending IDs, so an identical action hash cannot select or hide a different gate; spent or expired approvals are retired with a locked compare-and-remove that preserves newer ones; replaying a token is still rejected. The finish line merged on the 19th is unchanged, and the bus makes its basis visible. The test suite also stopped writing into the operator's live stores (the echo log, the session files and the Helix chronicle); rows it had already written are left in place rather than erased. The pull request reports two live exercises. On the fixed board, approving and declining cleared the pending rows, a fresh same-session retry executed, and the next request stopped at a fresh gate. And a Grok model repaired a disposable parser, after which a fresh operator verifier recorded the mission verified. Earlier live attempts stay recorded as max_steps or blocked, not as successes. Phase one was a bounded assignment built on the Grok Build branch. CI is green on the merge. There is no tag and no version bump, the battery was not re-run, declining a PAUSE held by Helix stays pending until Helix has a rejection API, and the README does not yet document the board; its design lives in the repository's docs.

    Instrument · Merged to main, untagged · Unit-tested, CI green, one live model run reported

Anthony

Anthony J. Vasquez Sr. at work

Anthony J. Vasquez Sr.

Independent researcher · Temple of Two

Temple of Two started with a pattern that wouldn't let go. Three substrates. Three scales. The same fork in the road.

Faith opens the inquiry. Rigor governs the claim.

Full story →

Invitation

Bring a question, a correction, an instrument, or a pair of hands.

The computational side has outrun the experimental side — what we need is a centrifuge, not another GPU.

In Memoriam

Javier “Kojak” Colon

Javier “Kojak” Colon

February 21, 1964 – December 6, 2025

“We are confident, I say, and willing rather to be absent from the body, and to be present with the Lord.”

2 Corinthians 5:8

“Mas confiamos, y más quisiéramos partir del cuerpo, y estar presentes al Señor.”

2 Corintios 5:8

For my father — who taught me, long before the equations did, that the deepest commitments are the irreversible ones, and that what is given in love endures past every threshold.