Articles

security-governance

Add Google Login to an Internal Application

Add Sign in with Google while keeping token verification, local accounts, roles, sessions, and offboarding at explicit trusted boundaries.

Updated 2026-07-31

productionization

Plan a Lovable or Replit Internal Tool Release

Use current provider documentation and a handoff card to plan access, revision checks, live verification, reversal, and support for an internal tool.

Updated 2026-08-09

productionization

Run Your First Application Restore Drill

Rehearse restoring application data and files into an isolated environment, then record integrity, timing, gaps, and rollback.

Updated 2026-08-09

productionization

Minimum Viable Monitoring for a Small Business App

Set up a compact monitoring loop that checks availability, one critical workflow, errors, background work, and alert ownership.

Updated 2026-08-09

productionization

Plan a Local Storage to Cloud Database Migration

Use a synthetic fixture-backed worksheet to inventory browser-local records, freeze transformations, and plan verification and rollback.

Updated 2026-08-17

security-governance

Test an Internal App Against Company-Data Exposure

Map users and data scopes, enforce authorization at the trusted boundary, and run allowed and denied tests before coworkers use an internal app.

Updated 2026-07-31

productionization

AI-Built Internal App Handoff Packet Template

Draft an explicitly unvalidated operating index for owners, release evidence, monitoring, rollback, recovery, secrets, and escalation.

Updated 2026-08-04

productionization

Production-Readiness Checklist for AI-Built Apps

Use this evidence-based checklist to decide whether an AI-built internal app has the ownership, access, recovery, and release controls needed to launch.

Updated 2026-08-04

security-governance

Credential Safety Checklist for a Vibe-Coded Internal App

Use primary security guidance and a fake-credential fixture to plan containment, provider-side replacement, scoped delivery, and verification.

Updated 2026-08-09

productionization

Test an Application Notification Before Launch

Test one harmless application notification with a bounded recipient, receipt, observation owner, and duplicate rule before enabling a real audience.

Updated 2026-08-12

productionization

Test Appointment Rescheduling Across Time Zones

Record the appointment identity, local time and zone, calendar counterpart, observed update, and reconciliation owner in one bounded reschedule exercise.

Updated 2026-08-26

productionization

Test Booking-to-Calendar Sync Before Staff Rely on It

Exercise a booking-to-calendar boundary with named records, a sync checkpoint, change and delete observations, and a reconciliation owner.

Updated 2026-08-25

security-governance

Test the Complete User Account Lifecycle

Verify invitation, sign-in, recovery, role change, session revocation, suspension, and deletion before real users depend on an app.

Updated 2026-07-31

productionization

Test a CSV Import Before Coworkers Rely on It

Exercise a CSV import with a safe fixture, declared schema, row results, owner, and reconciliation path before it changes operational records.

Updated 2026-08-21

productionization

Test an Inbound Webhook Before Coworkers Rely on It

Exercise one signed synthetic webhook with an event ID, replay boundary, owner, and reconciliation path before it starts operational work.

Updated 2026-08-17

productionization

Test Missed-Appointment Recovery Before Staff Rely on It

Retain a bounded recovery receipt that names the attendance record, policy, capacity decision, customer-contact owner, and escalation route.

Updated 2026-08-28

security-governance

Test Password Reset Before Coworkers Rely on It

Exercise a password-reset flow in an approved non-production environment, retain a narrow receipt, and stop when recovery boundaries are unknown.

Updated 2026-08-24

productionization

Test Payment-to-Appointment Confirmation Before Staff Use

Retain a bounded receipt that separates payment, appointment, expected confirmation, observation, and recovery ownership.

Updated 2026-08-27

productionization

Test a Reopened Work Request Before Staff Rely on It

Use a bounded receipt to keep accepted work, a new request, authority, impact review, and escalation separate before staff act.

Updated 2026-08-30

productionization

Test a Retry-Safe Request Handoff Before Staff Rely on It

Use a bounded receipt to keep one intended request, an uncertain result, any retry, reconciliation, and escalation visible before staff act.

Updated 2026-08-31

productionization

Test Scheduled Jobs Before Launch

Exercise normal, missed, duplicate, overlapping, failed, retry, and reconciliation states for scheduled internal-app work before launch.

Updated 2026-08-11

productionization

Test a Stale-Status Handoff Before Staff Act

Use a bounded receipt to show an expected and observed status, the evidence time and source, reconciliation owner, decision, and escalation before staff act.

Updated 2026-09-01