NEW CAPABILITY 06 / 06
Chat interfaces and scheduled routines
Where the system would meet the team, and what it would do while nobody is watching.
Mockups and a written mechanism. Nothing is running behind them.
Two designs rather than two demos. The first puts the assistant in the chat tool a team already lives in, with citations and a visible refusal. The second runs the routine work on a schedule and keeps a run history, including the runs that stopped at a gate.
THE DESIGN / MOCKUPS ONLY
What it would look like.
Interfaces and routines
Reaching people where they already work, and running while nobody is watching.
Two things a company brain needs once the facts are in order: a way to answer in the tools people already have open, and a way to do standing work on a clock. Both are drawn here as they would be built for the fictional Apex Instruments.
Design stage no live system, nothing connected, every screen below is a drawing
The same answer, in whichever window is already open
Two workspace styles, drawn in plain HTML and CSS. No product is connected and no product is endorsed. What matters is not the chrome around the message, it is that the answer carries its source and that a question with no approved source gets a refusal instead of a guess.
What is the priority turnaround on a calibration for a Care Plus site? A partner is asking on a call right now.
Two business days. The clock starts when the unit is checked in at the Tampa service center, Dock B. The standard line is three business days.
2 replies, last at 9:15 AM
While you are here, how long does a Field Kit run on one charge? I want it in the handout.
I cannot answer that from approved sources. A nine hour figure exists in the spec pack, revision C, but the row is marked provisional and no one has signed it. I have not used it.
The Marketing Lead was asked for the lab report on September 19. I will answer this the day it is signed.
0 approved sources · f-20 pendingAnswers are posted in the channel where the question was asked. Nothing is sent anywhere else.
What does Atlas Care Plus cost per unit per month? Quoting a four site rollout.
$149 per month per unit, list. The October price list replaced the handbook figure, so anything quoting the older number is out of date.
Good. Add the Northlight volume discount to the quote as well.
I cannot answer that from approved sources. The agreement summary states 12 percent, but it points to rate appendix B and that file was never supplied, so nothing ties the figure to a rate table.
Quote the list price and mark the discount as pending. The Account Manager requested appendix B on September 18.
0 approved sources · f-21 pendingReply
Select a callout, or a numbered marker on a mockup, to highlight the part it describes. Both mockups are hand drawn in HTML and CSS. No product logo, mark, or screenshot is used, and no product endorses this.
Four routines, and what happened the last time each one ran
Standing work on a clock: assemble a summary, check whether the facts have gone stale, audit links, rebuild the price sheet. Select any row to read its run log. This is a design for how the history would read, not a record of runs that happened.
- Passed finished, artifact produced
- Passed with warnings finished, something to look at
- Stopped at a gate refused to publish
- Skipped nothing had changed
| Routine and schedule | Last run | Duration | Outcome | Artifact |
|---|
A stopped run is a success for the person, not a failure. The price sheet rebuild reached a gate it was told never to cross, an unsigned figure heading for a published document, and it stopped there with the reason and the fact id. Nothing went out late, because nothing wrong went out at all. The failure case would have been publishing a 12 percent discount that no rate table supports, on time.
These four routines are a design. No scheduler is running, no artifact was produced, and the timestamps here are written to show the shape a real history would take.
THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE
How it works.
- 01Meet people
The assistant answers in the chat workspace, not in a separate app.
- 02Show the source
Every answer carries a citation chip that opens the document.
- 03Refuse in public
A refusal reads the same in a channel as it does on a web page.
- 04Run on time
Routines run on a schedule and write an artifact.
- 05Stop at the gate
A run that fails a check stops and says why, which counts as a success.
WHAT IT READS
- The approved-facts and citation behaviour from the other capabilities
- A schedule per routine
- A gate definition per routine
- A run log store
THE RULES IT HOLDS ITSELF TO
- A scheduled run always leaves a log, pass or fail
- A stopped run names the gate that stopped it
- Nothing posts to a channel without a citation or a refusal
- Access follows the same rules as the web assistant
This is a new capability, built for this portfolio. It is not part of a client engagement, and nothing here is connected to a company’s internal system. The sample company, Apex Instruments, does not exist.