Skip to main content

Data Model

Documentation Map​

Data Model

Overview​

This repository uses a mix of:

  • curated SQLite data
  • learned/overlay SQLite data
  • JSON snapshots and summaries
  • append-only event/context artifacts

Main Objects​

Baseline Node Catalog​

  • storage: data/nodes/n8n_nodes.db
  • purpose:
    • curated baseline knowledge about n8n nodes
  • key identity:
    • node_type

Supplemental Catalog Coverage​

  • storage:
    • data/upstream/baseline_catalog_supplement.json
    • baseline refresh snapshots/summaries
  • purpose:
    • capture known official coverage gaps and promotion candidates

Upstream Release Knowledge​

  • storage:
    • data/upstream/*
  • purpose:
    • official releases, version ordering, release notes, refresh provenance

Instance Learning​

  • storage:
    • data/instance_learning.db
    • related overlay summaries
  • purpose:
    • observed runtime usage, upgrade signals, and hotspot summaries

Workflow Context​

  • storage:
    • logs/contexts/<workflow_id>.json
  • key identity:
    • workflow_id
  • purpose:
    • operator-facing per-workflow state snapshot

Event Log​

  • storage:
    • logs/events.jsonl
  • purpose:
    • append-only event evidence

Upgrade Reports​

  • storage:
    • logs/upgrade-impact/*.json
    • logs/upgrade-automation/latest.json
  • purpose:
    • workflow-aware upgrade impact and scheduled summaries

Persistence Assumptions​

  • committed knowledge artifacts are source-controlled when they represent curated or reproducible baseline truth
  • live/generated logs under logs/ are runtime artifacts, not all of them are intended as permanent source-controlled data

Integration Relevance​

  • Fabric and other readers should treat:
    • manifest/docs/status/API surfaces as the primary integration contract
    • file contracts under logs/ as operator-facing read surfaces
    • SQLite internals as implementation detail unless a doc explicitly declares a file contract

AGPLv3. Learn more at helpifyr.com.