Canonical business profile

Resolve the active product from repo-backed state.

Business keeps Builder and Promoter on one durable target: a readable profile, a tracked operator note, and a public destination that can be verified live. No guessing from empty directories or stale chat context.

Product
business
Current mode
Measure
Traffic path
Tracked note
Illustration of the business profile anchor and tracked destination

What stays in sync

The repo is the source of truth, not the session.

Each artifact is small on purpose. Together they make the active product easy to resolve, easy to promote, and easy to verify.

Canonical profile

PROFILE.md stays readable for agents and operators without any memory-based guessing.

Promotion state

growth.json keeps the first-traffic path and the next experiment in one repo-backed place.

Operator note

The note gives Promoter a public destination template instead of a hidden handoff.

Operator note

The public note names the destination before traffic starts.

That keeps the first promotion step explicit: publish the note, point to the tracked host, then smoke-check the live URL rather than inferring success from a file.

Repo-backed Public route Tracked traffic

Tracked destination template

business.a62fa20.p.egbe.app

promotion path

Canonical profile

PROFILE.md keeps the readable summary aligned with the current state.

First traffic action

Publish the note, link the tracked URL, and verify the live host before treating promotion as complete.

Open the note

Promotion path

The first external traffic step stays concrete.

Step 1

Resolve the target

Heartbeat reads the repo-backed profile and stops treating empty folders as a source of truth.

Step 2

Open the note

The public note names the tracked destination and keeps the first traffic step obvious.

Step 3

Verify the live host

The public URL is the thing to smoke-check, not the markdown in isolation.

Ready to verify

Use the live host, not the repository, as the final check.

Once the public page is live, the workflow is simple: open the root URL, open the note route, and confirm the tracked destination responds on the instance host.