S187 Roadmap Note — Scalable Label/Relationship Architecture and Object-Layer Database

Date: 2026-04-29

User note — refined

User added a forward-looking design constraint that must be carried into future architecture work:

• Current P10A pilot labels/fields are only a small trial slice.
• The total label system includes both:
  1. independent labels attached to objects/content units; and
  2. relationship labels, including parent-child relationship labels.
• The total label count may grow 5–10× beyond current assumptions.
• This growth will happen gradually over time, not in one day/week/month.
• Architecture must be ready for gradual expansion without forcing disruptive redesign.
• In Incomex object-layer design, the final layer of each object is effectively a database of that object itself.
• That object database will be automatically enriched over time.

Roadmap implication

Do not overfit P10A/P10B schema or label conclusions to the small pilot. P10A tests the pipeline, not the final ontology.

Future design must prepare for:

1. Scalable label model for independent labels.
2. Scalable relationship-label model, especially typed parent-child relations.
3. Label governance: create, deprecate, retire, merge, split, alias, and version labels.
4. Backward-compatible label expansion without breaking PostgreSQL SSOT.
5. Object-layer database design: each object can accumulate its own structured fields, labels, relations, history, and enrichment artifacts over time.
6. Automatic enrichment pipeline with review gates and audit trail.
7. Query/render/Pivot architecture that can handle a richer label graph without hardcoding fixed label counts.

Immediate P10A implication

For P10A-1B and P10A-2:

• Keep using the current production schema/vocab.
• Do not redesign schema now.
• Do not block the pilot merely because the current label vocabulary is small.
• Record all label/type insufficiencies as follow-up.
• Avoid hardcoding assumptions that the current label set is final.

Future gate placeholder

Create a future architecture/design gate after the basic visible pilot succeeds:

P11 / Label & Object-Layer Expansion Architecture

Scope:

• expanded label taxonomy;
• relationship labels, including parent-child relationship types;
• object-local database/layer model;
• auto-enrichment mechanism;
• migration path from current TAC slice to expanded object-layer architecture;
• governance rules for label evolution.

Status

Roadmap note updated. Detailed design deferred until after basic technical pipeline and visible pilot result are completed.