NocoDB Foundation
Foundation contract
This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships.
Provenance and revision
- Source record:
nocodb; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index. - Recorded revision:
develop@640fe3b06fb26c9d000e2258477001c0d5e62c73. - Full provenance, coverage caveats, boundaries, and preserved evidence:
references/index.md.
Topic map
- Representative topics: Queue core; Worker admission; Enqueue contract; Event fan-out; Long-poll surface; Versioned migrations; Cache safety; Redis queue.
- Airtable LongText / PostgreSQL NUL (U+0000) removal, per-field coercion and
SingleSelect quirks:
references/import-record-coercion-ladder.md. - Scope and retrieval questions:
references/index.md#use-this-for. - Complete capsule chooser:
references/index.md#load-the-matching-source-dump. - Detailed grouped map:
references/index.md#capsule-map. - Source limitations and portability boundaries:
references/index.md#boundaries.
Retrieval
Choose a capsule from the topic map or index and load only the matching evidence. Capsules span revisions; use the selected capsule’s own file and pin, not the headline revision above. Revalidate that source before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.