Skip to main content

Synopsis

Display current status of schema, vault, and configuration.

Description

The status command provides a quick overview of:
  • Schema status - Current version, last modified, pending changes
  • Vault status - Registered versions, integrity, paranoid mode
  • Configuration - Debug settings and project config
Use this command to check project health and vault state.

Examples

Fresh Project (No Migrations)

Output:

After First Migration

Output:

Schema Modified (Pending Migration)

Output:

Multiple Versions

Output:

Integrity Issues

Output:

Status Fields

Schema Section

string
Latest registered schema version (e.g., v001, v002)
string
SHA256 hash of current version (first 12 characters)Example: 3f2a8b9c...
string
Time since last schema changeExamples:
  • just now
  • 5 minutes ago
  • 2 hours ago
  • 3 days ago
string
Current schema state:
  • βœ“ Up to date - No pending changes
  • ⚠️ Schema modified - Changes not yet migrated
  • ⚠️ No vault initialized - First-time setup needed

Vault Section

number
Total number of registered schema versionsExample: 3 registered
string
Cryptographic verification result:
  • βœ“ OK - All hashes verified
  • ❌ N issues - Tampering detected
string
Current paranoid mode:
  • πŸ›‘οΈ readonly - Schema locked (default)
  • βš™οΈ standard - Controlled changes allowed
  • πŸ‘‘ privileged - DBA access
  • 🚨 emergency - Incident recovery

Paranoid Mode Icons

Time Formatting

β€œLast modified” displays:
  • < 1 minute: just now
  • < 1 hour: N minutes ago
  • < 24 hours: N hours ago
  • β‰₯ 24 hours: N days ago

Common Status Patterns

Ready to Migrate

Action:

Locked in Readonly Mode

Action:

Integrity Violation

Action:

First-Time Setup

Action:

Troubleshooting

No Vault Initialized

Solution: Run first migration:

Cannot Read Vault

Solution: Ensure permissions:

Schema File Missing

Solution: Regenerate merged schema:

Quick Status Check Script

Integration Examples

Pre-Commit Hook

Monitoring Script

See Also