MuseField.org · Product-use rewrite

MuseField Product Trial

MuseField is becoming a live mUser-owned profile-world platform. The product must allow people to create, converse, mutate owned state, publish with consent, and use Muse — while money waits for MusePay and authority-bearing consequence stays reviewed.

main_merge_requires_human_review: true active_muse_guide: false interactive_prompting_enabled: false autonomous_suggestion_enabled: false deployment_readiness: false hq_route_link_visible: true implementation_patch_applied_on_branch: true root dashboard link -> authority visibility is not proof visibility is not authority visibility is not mutation does not activate Muse Root Workbench Review Corridor Static Muse panel candidate slot empty and held /archive/post-patch-rollback-receipt/ /data/root-workbench-implementation-patch.v0.json

live_instruction_intake: allowed_for_muser_owned_scope profile_mutation: allowed_by_owner world_birth: allowed_by_owner_declaration agent_assistance: allowed_with_permission economic_activation: blocked_until_musepay legal/government/certification claims: reviewed Headquarters profile: founder/developer cockpit

Headquarters Open Live HQ Observatory Open MuseFlow Academy Live Pilot

Main Headquarters

The Headquarters Archive is MuseField’s primary HQ

The established Headquarters Developer Profile remains the main founder and developer cockpit for MuseField: Map Composer, Context Spine, Event Record, Lane Index, Packet Preview, Review Lanes, and the wider governance and design lineage. It is not a background archive. Live HQ is a specialised read-only observatory for the Academy pilot and should extend the main Headquarters rather than replace it.

Headquarters Open Live HQ Observatory Headquarters Web Index Muse Instruction Field Archive MuseTrace Demo Post-patch rollback receipt Root workbench implementation patch Product Use JSON

Accessible now

MuseFlow Academy Live Pilot

Select or write several bounded instructions, inspect one ordered plan with exact intermediate and final bindings, record an owner decision, separately apply the accepted plan atomically, and open Live HQ to see the same private browser-local world, Talkback, events, and receipts.

Enter MuseFlow Academy Inspect Live HQ Observatory Headquarters

browser-local plan ≠ production Automation Order

Allowed ordinary use

Create and edit a mUser profile.
Talk with Muse and save instructions.
Create private worlds and publish owned worlds by declaration.
Mutate owned fields, projects, workspaces, and constellation visibility.
Use permissioned agents for profile, world, event, radio, market, research, and visibility help.

Money waits

Payments, payouts, wallets, custody, and real revenue claims remain blocked until MusePay exists.
Market listings may exist in non-payment mode.
Events and radio may publish in non-payment mode.

Authority stays scoped

No hidden public exposure.
No mutation outside owned or permissioned scope.
No unconsented private-data training.
No legal, government, certification, or identity-sensitive claims without review.

Trial mode

MuseField Trial Mode enables profiles, Muse chat, profile mutation, private worlds, owner-published public world pages, permissioned agents, non-payment events, non-payment radio, and non-payment market listings.

musepay: disabled

payment_processing: disabled_until_musepay

Development mode

Founder/developer mode may generate code candidates, invoke Builder, create Workcells, prepare patches, open draft PRs, and watch CI. Repo/system mutation still goes through Workcell, PR, checks, and human review.

deployment_readiness: false

autonomous_deploy: blocked

Core doctrine

Use is the product

Do not block use. Block unowned consequence, money, legal authority, hidden exposure, and unconsented action.

mUser-owned use allowedowner publication allowedMuse + agents allowed in scopeMusePay required for moneyauthority claims require reviewcross-user mutation blocked

Root gate compatibility

This section keeps the older root dashboard checks readable while Product Use Doctrine v1 becomes the newer product posture. On mobile, swipe inside the grid to read the compatibility cards.

Dashboard links · Colour key · dashboard-fields · dashboard-links

Cyan route: navigation and route clarity, not execution. Gold review: human attention to visual grammar, not approval. Rose risk. Violet candidate. White witness. Green available.

Glow does not mean permission. Gold does not mean approval. chat is not consent. not automatic action. visibility is not proof. visibility is not mutation. validator visibility is not permission. receipt visibility is not authority.

This static compatibility shell does not run validators, mutate the repo, open PRs, deploy, publish, or store private data. Product-use doctrine separately allows owned-scope action through scoped runtime surfaces.

Dashboard links

MuseFlow Academy Live Pilot · Headquarters · Live HQ Observatory · Visual Archive · Current State · Next Safe Rung · Review Receipt · World Boundary · World Receipt · Visual Memory Timeline · Visual Memory Comparison · World Creation

Colour key

Cyan route · Gold review · Rose risk · Violet candidate · White witness · Green available

Touched surfaces

Root Workbench Review Corridor · Static Muse panel candidate slot · empty and held

Evidence refs

/archive/post-patch-rollback-receipt/ · /data/root-workbench-implementation-patch.v0.json

Validator families

Website Gate · HQ Root Index Link Gate · Root Workbench Implementation Gate · Workbench Dropdown Rim Interface Gate

Receipt families

main_merge_requires_human_review: true · implementation_patch_applied_on_branch: true · active_muse_guide: false · interactive_prompting_enabled: false · autonomous_suggestion_enabled: false · deployment_readiness: false

Observed gaps / limits

Legacy gates still expect static shell tokens; Product Use Doctrine v1 is the newer product posture.

Blocked conversions

root dashboard link -> authority · root visibility -> permission · compatibility token -> doctrine rollback

Background question ladder

What does the mUser own? What can be changed directly? What requires review? What remains read-only? Which Headquarters surface is primary?

Next safe rungs

Keep Headquarters primary while adding the Live HQ Observatory as a bounded extension. Replace static-root gates only through explicit reviewed amendments.

Muse / mUser messages

Muse may help inside owned or permissioned scope. Static root tokens do not activate Muse. Headquarters visibility does not create authority.

Command seeds

Open Headquarters. Inspect Live HQ Observatory. Create product-use gate. Keep money blocked until MusePay.