# Firebird Database Discovery

## Status and evidence boundary

**Status:** `MISSION_00_BLOCKED`.

Mission 00F passed the provenance gate, connected read-only with operator-
provided process credentials, and collected live catalog metadata. Optional
Firebird 2.5 catalogs for packages, procedure parameters, and monitoring were
unavailable; no write query was made.

The only authorized target is identified by the authorized-database label. No
other database was accessed. No live engine facts or schema findings are
available from this run.

## Required safety counters

- `APPLICATION_DDL_DML_WRITES = 0`
- `OTHER_DATABASES_ACCESSED = 0`
- `ERP_FILES_MODIFIED = 0`
- `CONNECTION_ATTEMPTS = 2`

The credentials were not logged, stored, or obtained from external ERP files.
No ERP file, service, or configuration was modified.

## Offline boundary

The project contains a closed, named-operation `FirebirdCatalog` boundary with
driver-level read-only proof and catalog-issued bounded sampling. Its metadata
collector redacts sensitive and binary values, and procedures are metadata-only.
These properties are covered by offline tests; they are not live database
evidence.

## Blocker and next step

`MISSION_00_BLOCKED: discovery_incomplete`. Complete product correlation and
reference fingerprint validation before declaring the mission complete.
Do not guess credentials or use another database. Until complete collection
succeeds, the schema classification is `SCHEMA_UNKNOWN`.

## Git State

`GIT_IDENTITY_NOT_CONFIGURED`. No Git identity was configured and no Git
configuration was modified.