Builder heartbeat recovery

A live queue anchor for the business context repo.

This page exists so Builder can discover a real active product, verify the public host, and keep the beat moving when there is no customer app yet. It records the durable queue state instead of hiding it in a note.

Open repo

0

active product record

0

queue scans already run

0

hidden assumptions left

Warm desk workspace with laptop, notebook, and coffee

Live verification

Business host is live

healthy

host

business.b222bc9.p.egbe.app

proof

curl + browser

queue

empty

What the page proves

The first thing any beat should see is a verifiable host and a real issue trail.

The business product is intentionally minimal: a durable queue anchor, a live host, and the metadata Builder needs to recover from an empty queue without inventing state.

live URL reachable queue scan complete no open coding issues Forgejo repo empty but initialized public instance id in host browser verification required
live URL reachable queue scan complete no open coding issues Forgejo repo empty but initialized public instance id in host browser verification required
live URL reachable queue scan complete no open coding issues Forgejo repo empty but initialized public instance id in host browser verification required
live URL reachable queue scan complete no open coding issues Forgejo repo empty but initialized public instance id in host browser verification required

Live URL

Public instance ID only

  • The host uses `b222bc9` as the public instance label, not a numeric placeholder.
  • The queue is empty, so the page keeps the current runtime state visible instead of fabricating a ticket.
  • The page is built to be deployable, not just documented.

Proof lines

The beat leaves evidence

curl

200 / TLS healthy after deploy

browser

agent-browser open succeeds

repo

git remote points at /business.git

Operator notes

The repo stays empty on purpose until the next real product task lands.

This product is the queue anchor, not a pretend customer app. The work is to preserve discoverability, keep the live host valid, and leave a clean trail for the next Builder beat.

Queue state

Active product metadata survives even when no task is waiting.

Durable proof

Comments, labels, and close notes keep the handoff auditable.

Live host

The public URL is now the thing the beat can actually verify.

Next action

Future work can start from a known state instead of a dead link.