Skip to app details
Back to app library
APPNEURAL APP FAMILYOperations & Projects

Operations

Every shift's checks, incidents and handovers in one place

Run each location's day with checklists filled on a phone, an incident log, shift handovers and SOPs people must read.

01 / OVERVIEW

See where it fits in your day.

Locations have shifts (including shifts that cross midnight), the people who work there, incident types, due hours and a QR code. Checklist templates hold tick, yes or no, number with limits, text, choice and photo items, each with an optional SOP link; schedules (daily, weekdays or monthly, at shift start, shift end or a clock time, assigned to a role or a person) make due runs, a run keeps its own copy of the template, and a run not finished in its window is marked missed by the cron. The phone run screen saves each answer on the tap, asks for a note on a failing answer and offers to log an incident filled in with the item and reading. Incidents have type, severity, a due date from severity, an assignee, comments, root cause, corrective action, photos and a history through open, in progress, resolved and closed, with email to the assignee and, for high and critical, to managers and alert addresses when email is set up. Each location has a public report form at /report/<token> (QR code, on or off, new link on demand, honeypot and rate limits) where a visitor reports an issue without signing in. Handovers carry a summary, a task list, readings and the shift's runs and incidents, and the next shift acknowledges them by name. SOPs have steps with warnings and photos, an owner and review date, a version for each publish, must-read assignments by role and location with acknowledgements per version, and a print view. Home shows what is due now, missed today, open incidents, the last handover per location and SOPs to read. An API at /api/v1 with an API key or the workspace key lists locations, SOPs, runs, incidents and handovers and creates incidents, with a change feed; webhooks fire on incidents, runs and handovers. Three optional Claude features draft an SOP from a description, a checklist from an SOP and a handover from the shift's runs and incidents, and only draft; they are off without a key. There is no offline queue and no link to Assets yet

A LOOK INSIDEExample layout · sample content
Today at Main Street
ChecklistDueStatus
Opening checksoperationsEXAMPLE
Fridge temperatureschecklistEXAMPLE
Closing checksincidentEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Operations does for you.

01

Checklists and runs

Templates with tick, yes or no, number with limits, text, choice and photo items; schedules daily, on weekdays or monthly make runs due at shift start, shift end or a clock time, assigned to a role or a person, and a run not finished in its window is marked missed.

02

Incidents

A log with type, severity and a due date, an assignee, comments, root cause and corrective action, photos and a flow from open to closed; each location has a QR code that opens a public report form, so a visitor can report an issue without signing in.

03

Handovers and SOPs

Shift handovers carry a summary, a task list, readings and the shift's runs and incidents; SOPs have steps with warnings and photos, a version for each publish, owners, review dates and must-read acknowledgements by role and location.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Operations. What you can do depends on your access in the app.

01

Set up

Add locations and shifts, then print the QR code of each location.

02

Schedule

Build checklists from your SOPs and give each a schedule.

03

Run the day

Staff open the Home page, fill what is due, log incidents and hand over at the end of the shift.

YOUR NEXT MOVE

Make Operations part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Locations have shifts (including shifts that cross midnight), the people who work there, incident types, due hours and a QR code. Checklist templates hold tick, yes or no, number with limits, text, choice and photo items, each with an optional SOP link; schedules (daily, weekdays or monthly, at shift start, shift end or a clock time, assigned to a role or a person) make due runs, a run keeps its own copy of the template, and a run not finished in its window is marked missed by the cron. The phone run screen saves each answer on the tap, asks for a note on a failing answer and offers to log an incident filled in with the item and reading. Incidents have type, severity, a due date from severity, an assignee, comments, root cause, corrective action, photos and a history through open, in progress, resolved and closed, with email to the assignee and, for high and critical, to managers and alert addresses when email is set up. Each location has a public report form at /report/<token> (QR code, on or off, new link on demand, honeypot and rate limits) where a visitor reports an issue without signing in. Handovers carry a summary, a task list, readings and the shift's runs and incidents, and the next shift acknowledges them by name. SOPs have steps with warnings and photos, an owner and review date, a version for each publish, must-read assignments by role and location with acknowledgements per version, and a print view. Home shows what is due now, missed today, open incidents, the last handover per location and SOPs to read. An API at /api/v1 with an API key or the workspace key lists locations, SOPs, runs, incidents and handovers and creates incidents, with a change feed; webhooks fire on incidents, runs and handovers. Three optional Claude features draft an SOP from a description, a checklist from an SOP and a handover from the shift's runs and incidents, and only draft; they are off without a key. There is no offline queue and no link to Assets yet

Daily operations of a connected domain's locations and shifts: checklists and scheduled runs filled on a phone, an incident log with a public report form opened from a QR code, shift handovers acknowledged by the next shift, and SOPs with versions and must-read acknowledgements, with a home page of what is due, missed or open, an API with webhooks and a feed, and three optional AI drafting features.

Company equipment belongs to Assets; stock belongs to Inventory; customer support tickets belong to Support; approvals belong to Approvals; long-form documents belong to Writer and Documents.

Priority
P2
Portfolio
Operations & Projects
Capability
Operations & Projects
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:15
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

operation schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

operations.appneurox.com DEPLOYED

operations.appneurox.com

Worker
operation-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:15
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/operation-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app