Temple of Two

Independent inquiry · Anthony J. Vasquez Sr.

Where wonder
meets rigor.

Independent computational research tracing a common architecture of commitment across biological and computational substrates, where every claim is attached to a testable prediction, an open-source repository, and a DOI, and negative results are published alongside successes.

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.

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

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

    T2Helix 0.14.0: a failure is no longer learned from quoted text, and approval can be held for a human at a terminal

    Until this release the plugin tagged a shell call as a failure when its text contained words such as FAILED, a traceback or Error:. The hook sees only calls the harness accepted and receives no exit code, so that text was as often a deliberate failing test, a quoted traceback or a brief describing a failure as it was a real crash, and the tag could not tell which. Ambiguous text is now left untagged, as the module's own contract always said; interrupted calls still tag failure and clean calls still tag success. The changelog gives the measurement behind the change: on one machine, 109 shell calls were tagged as failures in two days, most of them on successful commands, and the rule that pauses on similar past failures issued 19 pauses in that window. The release also adds a switch, T2HELIX_REQUIRE_HUMAN_CONFIRM, off by default. With it on, a pending approval is accepted only from the command line, the text the model receives no longer names the script or the place tokens are listed, and the approval script refuses to run unless it is at a terminal with no agent session in its environment. Running that script from an agent's shell is denied; naming it in a commit message or a log query no longer is. The changelog states the limits: a pseudo-terminal still passes, so the terminal check is not proof of a human, and against an agent with a shell and write access to the store the switch is a speed bump, not a wall. The tool count is unchanged at fifteen.

    Instrument · Released, v0.14.0 on main · In use, local-only; switch off by default

  • Release

    Sovereign Stack v1.23.0: a search answers by relevance, and an empty one says where it looked

    Eleven planned tasks shipped behind existing seams, with no new store, no daemon and nothing that spends. Recall orders by relevance whenever a query is given and by newest only for a bare browse, and the reply says which order it used and whether that was the default. An empty search names the stores it searched and the ones it did not. A receipt that no longer matches its file says the file has moved on since the write, rather than that it was never verified. Signal counts are reported per source and never summed across sources. The heartbeat says whether the commit it serves is older than the one checked out, and says null with a reason when it cannot read git. Unknown arguments are refused on the write, governance and handoff tools. Every write path refuses to touch the live store while a test is running, and a census test keeps new writers under the same guard. The changelog reports 4,784 tests collected, 4,778 passed and 6 skipped at the final tree. The public heartbeat serves 1.23.0; no v1.23.0 tag has been pushed to the repository.

    Instrument · Living · v1.23.0, untagged · Live heartbeat

  • Release

    Sovereign Stack v1.22.0: the closes of earlier seats become a voice at arrival, and the retired reflector leaves the doors

    The release gathers 148 commits since 1.21.0. The 2026-09-07 entry already covers the first part of that span, so this one names what landed after it. Every session close writes what the seat learned, what surprised it and what it hands forward, and 149 of those closes sat in the store while no arrival door showed more than the newest. The Descent reads them back at arrival as a voice of its own, rebuilt from the store at read time with no clock, no model and no daemon: superseded closes drop out, a protected close is withheld whole, and an entry the reader cannot read is counted as unreadable rather than treated as absent. A new read tool, descend, returns the closes by month, seat or recurring shape with a coverage line. The arrival doors also stopped presenting the reflector, retired in August, as if it were still writing: its notes are gone from the doors, and a header that said "since last reflection" now says what it always measured, the newest entry written by a session close. Lineage letters are read by the next seat of the same model name. And one rule now decides which alerts need acknowledgement, read the same way by both stores that count them; a store that cannot be read reports unknown, never a healthy zero. The changelog reports 4,249 tests passed at the merge of that last change.

    Instrument · Living · tagged v1.22.0 · Live heartbeat

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.