Work products you can use, refine and keep.
Choose a working form for the result
A Living Surface is an interactive work product shaped around an objective. It can bring relevant information, controls and the next decision into a usable view. Instead of extracting an answer from a conversation, the person can inspect the result, compare inputs or refine the work in place.
The form should serve the task. A comparison may need adjustable assumptions; a review may need source context and a clear decision; a prepared deliverable may need careful reading rather than more controls. Interactivity is useful when it lets the person understand or carry forward the work.
The source and the view are different things
A surface presents information or authored work. Its visible state does not prove that every connected source is current, complete or authorized for everyone who can see the screen. A useful result identifies the context it uses and distinguishes source observations from assumptions supplied for an analysis.
Changing an input can change a calculation or presentation without changing an external system. If a control requests an external effect, that effect needs its own permitted operation and outcome. A model-generated interface cannot grant itself access through the controls it draws.
Continue with the same work product
The person can ask for a different comparison, a clearer presentation or additional useful behavior. Refinement should remain attached to the work being refined. A revised view must not quietly replace the original objective, reattribute another agent’s work or lose the assumptions needed to understand the result.
An agent can present a retained result in Home or make it available to authorized shared work. Rearranging the surrounding canvas changes presentation. It does not by itself cancel the originating agent, change its model assignment or widen its scope.
Keep the useful part as an App
A reusable App retains useful functionality for subsequent work. Saving an App and granting it access to a connected source are separate decisions. When it is reopened, it must operate with the sources and permissions currently available rather than inherit unrestricted access from the conversation that created it.
A saved artifact can remain valuable even when a connection is unavailable, but its limits must be clear. A historical view is not a fresh source read. An App that needs missing context should identify that requirement rather than produce a plausible substitute and call it live data.
Inspect behavior as well as appearance
A well-presented surface can still have incorrect assumptions or unusable controls. Evaluate the information it shows, how inputs affect the result, what a requested action would change and how failure is represented. A preview, a saved App and a confirmed external operation are different outcomes.
Not every document is executable, and not every surface has permission to make changes. Use the governance reference when evaluating a control that operates on a real system, and the continuity reference when evaluating what is retained, restored or available to the next task.
The public example has a defined boundary
On this website, surfaces and Apps use the public environment’s available example information and facts the visitor provides. Juniper Coffee’s names, prices and operating records are fictional. A useful on-site calculation can be real while the business it illustrates remains fictional.
Installed Cuttlefish can work with authorized real sources and native facilities. A public demonstration does not establish that a particular connector, platform release or organization has been configured. The Downloads, Enterprise and Security references help separate those questions.