Vibecode ServiceNow

You are building a lean indie version of ServiceNow.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# ServiceNow indie build

## Goal

Build the smallest trustworthy replacement for the core ServiceNow workflow for one developer or a tiny team.

## Scope

A local ticket queue with typed request forms, state transitions, an append-only audit log, and a tiny asset table you can link tickets to.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Automated discovery and a real CMDB that maps thousands of assets and their dependencies
- Change management and approval workflows that auditors and compliance frameworks already recognize
- Hundreds of prebuilt integrations into AD, Okta, Jira, SAP, monitoring tools and everything else in a corporate stack
- Role based access, SSO, data residency, and the enterprise security paperwork that comes with it
- An ecosystem of certified admins, partners and store apps, which is often the real reason the contract renews

If those capabilities are essential, use ServiceNow instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a local, single-user request queue called "Deskless". This is a personal consolation build for ServiceNow, not an ITSM platform. Be honest about scope.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind.
- SQLite via better-sqlite3, file at ./data/deskless.db, schema created on boot if missing.
- Server Actions for all mutations. No API routes unless needed.
- No auth, no accounts, no telemetry, no cloud. It runs at localhost:3000 for one person.

Data model:
- assets: id, name, kind (laptop, service, subscription, account), owner_note, created_at.
- tickets: id, key (auto like REQ-0001), title, body, type (incident, request, change), priority (low, med, high), state (new, in_progress, waiting, done, cancelled), asset_id nullable, due_date nullable, created_at, updated_at.
- events: id, ticket_id, at, kind (created, state_change, comment, field_change), from_value, to_value, note. Append only, never edited or deleted.

Features in scope:
- Ticket list with filters by state, type, priority, and a text search over title and body.
- New ticket form where the fields shown change by type: change tickets additionally ask for rollback_plan and planned_window, stored as JSON in an extra_fields column.
- Ticket detail page: state transition buttons, comment box, linked asset, and the full audit log rendered as a timeline.
- Assets page: create, list, and see all tickets touching an asset.
- A "Weekly" view: tickets closed in the last 7 days and anything still open past its due date.
- Export everything to a single JSON file via a button, and a CSV export of tickets.

Explicitly out of scope, do not build: SLAs, approval chains, discovery agents, email ingestion, multi-user roles, SSO, a workflow designer.

Deliver: a README with setup in three commands, a seed script that inserts 12 sample tickets and 5 assets, and one Vitest file covering that state changes always write an events row.

## Required capabilities

- Node 20+
- A browser
- Nothing else, it runs on local SQLite

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of ServiceNow.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# ServiceNow indie build

## Goal

Build the smallest trustworthy replacement for the core ServiceNow workflow for one developer or a tiny team.

## Scope

A local ticket queue with typed request forms, state transitions, an append-only audit log, and a tiny asset table you can link tickets to.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Automated discovery and a real CMDB that maps thousands of assets and their dependencies
- Change management and approval workflows that auditors and compliance frameworks already recognize
- Hundreds of prebuilt integrations into AD, Okta, Jira, SAP, monitoring tools and everything else in a corporate stack
- Role based access, SSO, data residency, and the enterprise security paperwork that comes with it
- An ecosystem of certified admins, partners and store apps, which is often the real reason the contract renews

If those capabilities are essential, use ServiceNow instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a local, single-user request queue called "Deskless". This is a personal consolation build for ServiceNow, not an ITSM platform. Be honest about scope.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind.
- SQLite via better-sqlite3, file at ./data/deskless.db, schema created on boot if missing.
- Server Actions for all mutations. No API routes unless needed.
- No auth, no accounts, no telemetry, no cloud. It runs at localhost:3000 for one person.

Data model:
- assets: id, name, kind (laptop, service, subscription, account), owner_note, created_at.
- tickets: id, key (auto like REQ-0001), title, body, type (incident, request, change), priority (low, med, high), state (new, in_progress, waiting, done, cancelled), asset_id nullable, due_date nullable, created_at, updated_at.
- events: id, ticket_id, at, kind (created, state_change, comment, field_change), from_value, to_value, note. Append only, never edited or deleted.

Features in scope:
- Ticket list with filters by state, type, priority, and a text search over title and body.
- New ticket form where the fields shown change by type: change tickets additionally ask for rollback_plan and planned_window, stored as JSON in an extra_fields column.
- Ticket detail page: state transition buttons, comment box, linked asset, and the full audit log rendered as a timeline.
- Assets page: create, list, and see all tickets touching an asset.
- A "Weekly" view: tickets closed in the last 7 days and anything still open past its due date.
- Export everything to a single JSON file via a button, and a CSV export of tickets.

Explicitly out of scope, do not build: SLAs, approval chains, discovery agents, email ingestion, multi-user roles, SSO, a workflow designer.

Deliver: a README with setup in three commands, a seed script that inserts 12 sample tickets and 5 assets, and one Vitest file covering that state changes always write an events row.

## Required capabilities

- Node 20+
- A browser
- Nothing else, it runs on local SQLite

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of ServiceNow.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# ServiceNow product brief

## Problem

You can build a ticket tracker in an afternoon. You cannot build ServiceNow, because ServiceNow is not a ticket tracker: it is a CMDB, an approval engine, a change management workflow that auditors accept, and a discovery agent crawling every asset on a corporate network. Nobody buys it because the forms are nice, they buy it because Sarbanes-Oxley auditors and ISO reviewers already know what a ServiceNow change record looks like. The personal version of this makes no sense either, since a single human does not need a change advisory board. If you genuinely want the shape of it for yourself, build a small request queue with states and an audit log and stop there.

## Product outcome

A local ticket queue with typed request forms, state transitions, an append-only audit log, and a tiny asset table you can link tickets to.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Node 20+
- A browser
- Nothing else, it runs on local SQLite

## Explicit non-goals for v1

- Automated discovery and a real CMDB that maps thousands of assets and their dependencies
- Change management and approval workflows that auditors and compliance frameworks already recognize
- Hundreds of prebuilt integrations into AD, Okta, Jira, SAP, monitoring tools and everything else in a corporate stack
- Role based access, SSO, data residency, and the enterprise security paperwork that comes with it
- An ecosystem of certified admins, partners and store apps, which is often the real reason the contract renews

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build a local, single-user request queue called "Deskless". This is a personal consolation build for ServiceNow, not an ITSM platform. Be honest about scope.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind.
- SQLite via better-sqlite3, file at ./data/deskless.db, schema created on boot if missing.
- Server Actions for all mutations. No API routes unless needed.
- No auth, no accounts, no telemetry, no cloud. It runs at localhost:3000 for one person.

Data model:
- assets: id, name, kind (laptop, service, subscription, account), owner_note, created_at.
- tickets: id, key (auto like REQ-0001), title, body, type (incident, request, change), priority (low, med, high), state (new, in_progress, waiting, done, cancelled), asset_id nullable, due_date nullable, created_at, updated_at.
- events: id, ticket_id, at, kind (created, state_change, comment, field_change), from_value, to_value, note. Append only, never edited or deleted.

Features in scope:
- Ticket list with filters by state, type, priority, and a text search over title and body.
- New ticket form where the fields shown change by type: change tickets additionally ask for rollback_plan and planned_window, stored as JSON in an extra_fields column.
- Ticket detail page: state transition buttons, comment box, linked asset, and the full audit log rendered as a timeline.
- Assets page: create, list, and see all tickets touching an asset.
- A "Weekly" view: tickets closed in the last 7 days and anything still open past its due date.
- Export everything to a single JSON file via a button, and a CSV export of tickets.

Explicitly out of scope, do not build: SLAs, approval chains, discovery agents, email ingestion, multi-user roles, SSO, a workflow designer.

Deliver: a README with setup in three commands, a seed script that inserts 12 sample tickets and 5 assets, and one Vitest file covering that state changes always write an events row.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted ServiceNow capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# ServiceNow indie build

## Goal

Build the smallest trustworthy replacement for the core ServiceNow workflow for one developer or a tiny team.

## Scope

A local ticket queue with typed request forms, state transitions, an append-only audit log, and a tiny asset table you can link tickets to.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Automated discovery and a real CMDB that maps thousands of assets and their dependencies
- Change management and approval workflows that auditors and compliance frameworks already recognize
- Hundreds of prebuilt integrations into AD, Okta, Jira, SAP, monitoring tools and everything else in a corporate stack
- Role based access, SSO, data residency, and the enterprise security paperwork that comes with it
- An ecosystem of certified admins, partners and store apps, which is often the real reason the contract renews

If those capabilities are essential, use ServiceNow instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build a local, single-user request queue called "Deskless". This is a personal consolation build for ServiceNow, not an ITSM platform. Be honest about scope.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind.
- SQLite via better-sqlite3, file at ./data/deskless.db, schema created on boot if missing.
- Server Actions for all mutations. No API routes unless needed.
- No auth, no accounts, no telemetry, no cloud. It runs at localhost:3000 for one person.

Data model:
- assets: id, name, kind (laptop, service, subscription, account), owner_note, created_at.
- tickets: id, key (auto like REQ-0001), title, body, type (incident, request, change), priority (low, med, high), state (new, in_progress, waiting, done, cancelled), asset_id nullable, due_date nullable, created_at, updated_at.
- events: id, ticket_id, at, kind (created, state_change, comment, field_change), from_value, to_value, note. Append only, never edited or deleted.

Features in scope:
- Ticket list with filters by state, type, priority, and a text search over title and body.
- New ticket form where the fields shown change by type: change tickets additionally ask for rollback_plan and planned_window, stored as JSON in an extra_fields column.
- Ticket detail page: state transition buttons, comment box, linked asset, and the full audit log rendered as a timeline.
- Assets page: create, list, and see all tickets touching an asset.
- A "Weekly" view: tickets closed in the last 7 days and anything still open past its due date.
- Export everything to a single JSON file via a button, and a CSV export of tickets.

Explicitly out of scope, do not build: SLAs, approval chains, discovery agents, email ingestion, multi-user roles, SSO, a workflow designer.

Deliver: a README with setup in three commands, a seed script that inserts 12 sample tickets and 5 assets, and one Vitest file covering that state changes always write an events row.

## Required capabilities

- Node 20+
- A browser
- Nothing else, it runs on local SQLite

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# ServiceNow product brief

## Problem

You can build a ticket tracker in an afternoon. You cannot build ServiceNow, because ServiceNow is not a ticket tracker: it is a CMDB, an approval engine, a change management workflow that auditors accept, and a discovery agent crawling every asset on a corporate network. Nobody buys it because the forms are nice, they buy it because Sarbanes-Oxley auditors and ISO reviewers already know what a ServiceNow change record looks like. The personal version of this makes no sense either, since a single human does not need a change advisory board. If you genuinely want the shape of it for yourself, build a small request queue with states and an audit log and stop there.

## Product outcome

A local ticket queue with typed request forms, state transitions, an append-only audit log, and a tiny asset table you can link tickets to.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Node 20+
- A browser
- Nothing else, it runs on local SQLite

## Explicit non-goals for v1

- Automated discovery and a real CMDB that maps thousands of assets and their dependencies
- Change management and approval workflows that auditors and compliance frameworks already recognize
- Hundreds of prebuilt integrations into AD, Okta, Jira, SAP, monitoring tools and everything else in a corporate stack
- Role based access, SSO, data residency, and the enterprise security paperwork that comes with it
- An ecosystem of certified admins, partners and store apps, which is often the real reason the contract renews

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build a local, single-user request queue called "Deskless". This is a personal consolation build for ServiceNow, not an ITSM platform. Be honest about scope.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind.
- SQLite via better-sqlite3, file at ./data/deskless.db, schema created on boot if missing.
- Server Actions for all mutations. No API routes unless needed.
- No auth, no accounts, no telemetry, no cloud. It runs at localhost:3000 for one person.

Data model:
- assets: id, name, kind (laptop, service, subscription, account), owner_note, created_at.
- tickets: id, key (auto like REQ-0001), title, body, type (incident, request, change), priority (low, med, high), state (new, in_progress, waiting, done, cancelled), asset_id nullable, due_date nullable, created_at, updated_at.
- events: id, ticket_id, at, kind (created, state_change, comment, field_change), from_value, to_value, note. Append only, never edited or deleted.

Features in scope:
- Ticket list with filters by state, type, priority, and a text search over title and body.
- New ticket form where the fields shown change by type: change tickets additionally ask for rollback_plan and planned_window, stored as JSON in an extra_fields column.
- Ticket detail page: state transition buttons, comment box, linked asset, and the full audit log rendered as a timeline.
- Assets page: create, list, and see all tickets touching an asset.
- A "Weekly" view: tickets closed in the last 7 days and anything still open past its due date.
- Export everything to a single JSON file via a button, and a CSV export of tickets.

Explicitly out of scope, do not build: SLAs, approval chains, discovery agents, email ingestion, multi-user roles, SSO, a workflow designer.

Deliver: a README with setup in three commands, a seed script that inserts 12 sample tickets and 5 assets, and one Vitest file covering that state changes always write an events row.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted ServiceNow capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR