Everbind

The activity changed. The commitment didn’t.

A schedule comparison can show that Activity A was retired and replacement activities B and C were added. It does not by itself establish which new work inherits A’s existing commitment.

Everbind preserves that continuity across revisions. Gemini proposes possible lineage; when the evidence is ambiguous, the system abstains and requests the one clarification that changes the decision. Deterministic CPM then evaluates the revision, human authority alone can change the accepted schedule record, and a separate process reconstructs the result from retained bytes.

Demo scenario

The four-minute demo uses fixed, reproducible synthetic schedule revisions anchored to retained public-source documents.

Revision 18 retires Activity A and introduces B and C. The package does not establish which new activity inherits A’s January 23 commitment, so Everbind pauses acceptance rather than guessing.

After contractor clarification and an evidence-backed reviewer record, deterministic CPM shows that the inherited work still finishes four days late. Revision 18 is returned with comments, while the accepted schedule remains unchanged.

Revision 19 passes the same evaluation, but does not become effective until an authorized reviewer accepts the exact reviewed bytes. A separate process then reconstructs the receipt from retained transaction data.

How the transaction works

1. Gemini through Google ADK proposes possible lineage using a closed schema.
2. Every proposal is checked against retained source evidence and known project IDs.
3. If lineage is unresolved, Everbind pauses acceptance and drafts a clarification request.
4. A reviewer records the contractor’s evidence-backed mapping; the reviewer does not design the contractor’s work.
5. Deterministic CPM recomputes dates, float, commitment compliance, and protected drift.
6. An ineligible revision is returned with comments and cannot modify the accepted schedule.
7. Only an authorized reviewer can accept an eligible revision, and that authorization is bound to the exact reviewed bytes.
8. A separate process reconstructs the transaction and emits a replayable receipt.

Google Cloud and model roles

• Gemini 3.5 on Vertex AI: proposes bounded semantic lineage; it cannot emit schedule days, authorization, entitlement, or accepted-state mutation.
• Google ADK: provides the closed-schema proposal interface around the model call.
• Cloud Storage and Firestore: retain create-only evidence bytes and their binding manifest in the prior authenticated proof path.
• Cloud Run: hosted the recorded Judge transaction and a separate read-only evidence verifier. The paid endpoint is intentionally not advertised here.
• Gemma: provides a retained advisory receipt outside the decision path.

Execution boundaries

Executed during the recorded transaction:

• lineage and abstention state transitions;
• clarification and evidence-backed mapping records;
• deterministic CPM recomputation;
• eligibility and human-authority gates;
• the accepted-schedule transition;
• independent cold replay.

Retained rather than freshly generated during that transaction:

• the Gemini/ADK semantic proposal;
• the authenticated Google Cloud evidence bundle;
• Gemini Image, Vision QA, and Veo presentation media.

Optional presentation assets

After an authorized acceptance, Everbind can produce a receipt-bound, non-binding change brief using Gemini Image, Vision QA, and Veo. These assets do not participate in eligibility, authorization, or accepted-state mutation.

Run locally

Requires Python 3.12+ and uv.

uv sync --frozen --extra dev --extra google
rm -rf /tmp/everbind-review
uv run python -m construction_partner.serve \
  --surface hero \
  --workspace /tmp/everbind-review \
  --host 127.0.0.1 \
  --port 8080

Open http://127.0.0.1:8080. The standard launcher is intentionally loopback-only.

Validate

uv run pytest -o addopts='' \
  tests/test_release_cleanliness.py \
  tests/test_everbind_core.py \
  tests/test_public_judge.py \
  tests/test_c1_gate5.py \
  tests/test_c1_gate6_contract.py \
  tests/test_c1_gate6_semantic.py \
  tests/test_c1_gate6_standing.py \
  tests/test_c1_gate7_backend.py \
  tests/test_c1_gate7_e2e.py \
  tests/test_c1_gate7_lineage.py \
  tests/test_c1_gate7_revision_review.py \
  tests/test_c1_gate7_visual_shell.py
uv run ruff check src tests

Limits

Everbind is a bounded synthetic owner-side fixture, not production construction software. It does not claim current P6/XER ingestion, general P6 equivalence, practitioner validation, production identity, external contractor/CDE integration, or legal, permit, entitlement, payment, or contractual effect.

Evidence boundaries and provenance

Bundled public-source documents retain their original bytes and claim limits and are not covered by this repository’s MIT license. Model-generated media is non-binding presentation material. Media-generation receipts document those assets; verification receipts are produced independently by the deterministic transaction and cold-replay paths.

See THIRD_PARTY_NOTICES.md, PROVENANCE.md, evidence/c1-public-judge/README.md, and docs/c1/GOOGLE_LIVE_PROOF.md.