API incident notebook.
The engineering brief.

Record manually supplied incidents and investigation notes without fabricated live observability.

Operations & developer workspaces · Authored October 27, 2026 · Curated specification, not a claim of a completed production build

A connected route plan.

Home
Login
Register
incidents workspace
Record detail
Profile

Specific interaction

Provide severity/status filtering and a chronological note editor; label all inputs as operator-maintained.

Acceptance check

Confirm no chart or status claims a connected monitoring feed when none exists.

The starting data contract.

incidents · 3 typed fields

title: string · required
severity: string · required
status: string · required

notes · 2 typed fields

title: string · required
body: string · required

Capabilities

Database · Visitor auth. The brief requires real supported integrations; missing services must stay explicitly unavailable.

Design direction

Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure.

The complete prompt.

Edit business facts, service boundaries and the first-release scope before building. The specification is original public documentation, not a customer project source bundle.

PRODUCT AND OUTCOME
Build api incident notebook. Record manually supplied incidents and investigation notes without fabricated live observability. Provide severity/status filtering and a chronological note editor; label all inputs as operator-maintained.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, incidents workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"incidents","fields":{"title":{"type":"string","required":true},"severity":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"incidents","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm no chart or status claims a connected monitoring feed when none exists. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Related workflows.

Questions before you choose.

What does the api incident notebook prompt include?

It defines 6 route roles, the incidents and notes collections, specific interactions, design direction and an acceptance check. Review the supplied requirements before asking the builder to implement them.

Does preparing this prompt start a build or spend usage?

No. The action saves the exact editable brief and opens project naming or authentication. Generation starts only when you explicitly send the prompt. Copying the text makes no model request.

Are the generated app and services included in a $4.99 source unlock?

The one-time unlock grants source access for one project. Generation, hosting and external services are separate. Managed authentication, data, AI and payments remain hosted dependencies unless migrated or replaced; private records and credentials are not in the export.

Check the architecture. Compare the tradeoffs.

Follow the data model, account boundary and source handoff before choosing a builder.