Tutorial: the demo story

Do this: Open "Demo controls" and choose "Applicant".

You should see: You land on the City of Acme home page, signed in as the applicant.

Go to this screen Opens as Applicant.

Do this: Click "Apply for a permit".

You should see: The "Permits and applications" page opens.

Go to this screen Opens as Applicant.

Do this: Click "Start an application".

You should see: The page "Start an application" lists the permit types as cards.

Go to this screen Opens as Applicant.

Do this: Click the "Residential deck or fence" card.

You should see: The application form opens.

Go to this screen Opens as Applicant.

Do this: Choose "Fence". Type the property address "400 Lantern Row" and pick the suggested address. Type the fence height 6. Leave the rest blank.

You should see: The form accepts what you typed. Nothing is saved until you press "Submit application".

Go to this screen Opens as Applicant.

Do this: Click "Submit application".

You should see: A summary headed "There is a problem" lists every missing item, and a message sits beside each field. Everything you typed is kept.

Go to this screen Opens as Applicant.

Do this: Fix each item: Fence material cedar; Location on the property "Side or rear yard"; Distance from the property line 2; tick "I will not build over the property line"; add a Project description; Email demo.applicant@example.invalid; add a Site sketch and a Material specification with "Add file" (a small text file works); tick the certification.

You should see: Each message beside a field goes away once the field is complete.

Go to this screen Opens as Applicant.

Do this: Click "Check my application".

You should see: The findings are grouped under "Must fix", "Should check" and "Looks good", and each one names the published rule behind it. The button carries a Muse badge, and Muse explains the result in plain words when it is live. A "Must fix" holds "Submit application" until the applicant presses "Submit anyway" and writes a reason.

Go to this screen Opens as Applicant.

Do this: Click "Submit application" again.

You should see: A receipt headed "Application received" shows your reference number and the status "Awaiting intake agent".

Go to this screen Opens as Applicant.

Do this: Click "Track application", or "My permits" in the top menu.

You should see: "My permits" lists your applications under the tabs Active, Drafts and Closed.

Go to this screen Opens as Applicant.

Do this: Click "Start an application", then "Residential deck or fence". Click "Ask" at the corner of the page, type "Do I need a permit for a 6 ft fence?" under "Your question" and click "Ask".

You should see: The answer shows the label that says where it came from: "Recorded demo answer" for a stored answer, which cites ACME Code §14-305 and §14-306, and "Muse Spark (live)" for a live answer.

Go to this screen Opens as Applicant.

Do this: Open "Demo controls" and choose "Agent Operator".

You should see: You land on "Agents". The counts read "Waiting", "Running" and "Failed". Under "Agent status" the Intake agent reads asleep.

Go to this screen Opens as Agent Operator.

Do this: Click "Intake agent" in the left menu.

You should see: The heading reads "Waiting work" with the number of cases that wait beside it. The page says "The agent is asleep, so the run buttons are off." Open "More details" to read "Processing" and "Engine".

Go to this screen Opens as Agent Operator.

Do this: Click "Wake agent".

You should see: The button now reads "Put agent to sleep". The batch button reads Process N cases, or Process the next 20 of N when more than 20 cases are waiting. When no case waits, the note beside it reads "Nothing is waiting".

Go to this screen Opens as Agent Operator.

Do this: Under "Waiting work", click "Process one" on the fence case, or press the batch button. It reads Process N cases, or Process the next 20 of N when more than 20 cases are waiting.

You should see: The case leaves the table. Read "Last run" for what the run did, and open "More details" to read "Recent results". Read "Needs attention" for work that failed, and click "Try again" on a row to run it again. If the table says "Nothing is waiting for this agent.", send an application as the Applicant first.

Go to this screen Opens as Agent Operator.

Do this: Open "Agent runs" in the left menu, then click "View run" on the row for the fence case.

You should see: "Run detail" shows "Processing mode", "Processing steps" and "Recorded business changes". These runs use "Built in logic". No model was called.

Go to this screen Opens as Agent Operator.

Do this: Open "Steward assistant" in the left menu and click "Wake agent". Leave it awake.

You should see: The steward assistant reads awake and the button reads "Put agent to sleep". Under "More details" the counts read "Recommendations", "High", "Review" and "Held". Click "Prepare recommendations" to prepare the work of the queue, or leave it to the Data Steward.

Go to this screen Opens as Agent Operator.

Do this: Open "Demo controls" and choose "Data Steward".

You should see: You land on "Data issues".

Go to this screen Opens as Data Steward.

Do this: Wake the steward assistant at the top of the page: click "Wake".

You should see: The panel says the steward assistant is awake and the button reads "Put to sleep". The change is recorded with your name. While it sleeps, "Prepare recommendations" is off and the note says "Press Wake to wake it." The Agent Operator can wake it too.

Go to this screen Opens as Data Steward.

Do this: Click "Prepare recommendations".

You should see: Each task the assistant works on gets a "High", "Review" or "Held" pill and a one-line reason under the record. A "High" pill means the assistant is sure of its proposal, "Review" means read the evidence first, and "Held" means the facts disagree and only a person may settle it.

Go to this screen Opens as Data Steward.

Do this: Open a task of the queue and read the panel "The steward assistant".

You should see: It shows the pill, the reason and the evidence the assistant rests on. Edit the "Reason" if you wish, then click "Accept recommendation". The decision is recorded with your name. A "Held" recommendation is never accepted: read the conflicting facts and decide it yourself with the actions under "5. What will this action do?".

Go to this screen Opens as Data Steward.

Do this: To turn a proposal down, click "Clear recommendation" and decide the task yourself.

You should see: The recommendation is set aside and the task holds no answer. A recommendation for a record match may propose to reject the proposed link; accepting it records that rejection in your name.

Go to this screen Opens as Data Steward.

Do this: Back on "Data issues", click "Accept all high-confidence". The button shows how many.

You should see: A page lists exactly the recommendations the batch would accept. Click "Accept these" with the count to confirm the list. An item that changed since the list was made is skipped and named, never accepted silently.

Go to this screen Opens as Data Steward.

Do this: Open the task that names the fence case and read the panel "Submitted vs record".

You should see: It sets what the applicant submitted beside what the record holds today and writes the difference in words. On the case of the permit, click "Open the original submission" to read the application as it arrived; that page is read only.

Go to this screen Opens as Data Steward.

Do this: To close a data issue that needs no change, click "Start" under "Close with a reason".

You should see: Choose "Close as" and "Reason", write the "Note", and submit. The issue closes with your name, the time and the reason. A permit decision is a separate step.

Go to this screen Opens as Data Steward.

Do this: Open "More tools" in the left menu, then click "Work queue".

You should see: A case whose parcel link is not confirmed carries the tag "Data follow-up: parcel not confirmed". The agent recommends on the rules it checked and does not wait for the steward; the open parcel link stays a follow-up, and the steward can fix the record at any stage, before or after the review, the decision or the issue. Missing information from the applicant still goes back to the applicant, and the payer link and the fee still block issuing.

Go to this screen Opens as Data Steward.

Do this: Click "Master records" in the left menu and open the tab "People and organizations".

You should see: The list shows the master records. A master record is the one agreed version of a person or organization.

Go to this screen Opens as Data Steward.

Do this: Open "Demo controls" and choose "Permit Reviewer".

You should see: You land on the "Work queue". A case the City sent back to the applicant reads "Waiting for the applicant's answer" in the issue column.

Go to this screen Opens as Permit Reviewer.

Do this: Open "Review queue" and open the fence case.

You should see: The permit workspace opens for that application. The page folds its parts into sections, such as "Where this case is", "Next action", "Outstanding issues", "Application checks", "Decision" and "Actions". The "Decision" section starts open when the next action is to decide or to read the decision.

Go to this screen Opens as Permit Reviewer.

Do this: Click the tabs "Documents", "People and organizations", "Activity" and "Review" in turn.

You should see: Each tab shows one part of the case: the files sent in, the people and the organizations, what has happened, and the review.

Go to this screen Opens as Permit Reviewer.

Do this: On the "People and organizations" tab, click "Start" under "Confirm parcel" and submit it.

You should see: The page updates in place and keeps the tab.

Go to this screen Opens as Permit Reviewer.

Do this: On the "Review" tab, click "Start" under "Run application checks" and submit it.

You should see: The rule results appear. A check that could not run because the parcel is not confirmed is listed as Not checked. An open parcel or identity link is Data follow-up: it is separate from the rule results and does not refuse the decision.

Go to this screen Opens as Permit Reviewer.

Do this: Click "Start" under "Record review decision". Choose "Approve", write the "Rationale (internal record)" and click "Record the decision".

You should see: An open parcel or identity link does not refuse the approval. The case shows Data follow-up, and the Data Steward can confirm it afterwards. A check that was not run because the parcel is not confirmed is listed as Not checked; the reviewer decides whether to approve against it and records an "Exception reason" when required. After an approval, "Issue permit" is refused until the fee is assessed, paid and reconciled. The payer account is still required to apply a payment and to issue.

Go to this screen Opens as Permit Reviewer.

Do this: To send the case back to the applicant, open the same form and choose "Needs information".

You should see: The "Rationale (internal record)" is filled with the request for you. Write the rest, click "Record the decision", and the case goes back to the applicant. The City assesses the application again from the start.

Go to this screen Opens as Permit Reviewer.

Do this: Open "Demo controls" and choose "City Administrator".

You should see: You land on the planning overview.

Go to this screen Opens as City Administrator.

Do this: Open "More tools" in the left menu, then click "What-if".

You should see: The page lists suggestions and your saved what-ifs.

Go to this screen Opens as City Administrator.

Do this: Under "Start from an example" click "Raise the side/rear fence height limit from 6 ft to 7 ft".

You should see: The editor opens. When the synthetic year (sample data) is loaded, the seed 20261028 and the case count 600 are already filled in.

Go to this screen Opens as City Administrator.

Do this: Click "Run comparison".

You should see: The results page compares the current rule with the change. With the prepared sample data, 600 cases are tested and 28 of them change outcome: approvals go from 306 to 334 and denials from 80 to 52.

Go to this screen Opens as City Administrator.

Do this: Click "Read briefing". When live Muse is on, click "Write the briefing with Muse". When it is off, click "Try recorded Muse briefing".

You should see: When the call is live the label reads "Muse briefing (live)". When it is a recorded answer the label reads "Recorded Muse briefing". The sections are Summary, Key effects, and Risks and trade-offs. The hosted demonstration is set for 100 live Muse calls per deploy and 100 provider calls a day, and whoever runs it can change that setting. When the allowance is used up, the recorded answer is used.

Go to this screen Opens as City Administrator.

Do this: Go back to the results page and click "Save as a draft rule change".

You should see: The change is saved as a draft with the status "Draft: ready for your approval". Click "Open the draft" to approve and publish it on Rules and fees. If your city uses independent approval, the status reads "Draft: needs independent approval" and the reason beside the disabled buttons says you authored this version: another administrator must approve it, and another must publish it.

Go to this screen Opens as City Administrator.

Do this: Open "More tools" in the left menu, then open "City view", "Operations dashboard", "Audit log", "Support" and "Checks".

You should see: Each page loads. The Operations dashboard shows the figures, and the Audit log shows what each person and system did.

Go to this screen Opens as City Administrator.