A read-only threshold gate that defines when categories stay shared, become partitioned branches, move to dedicated domain registries, require root promotion review, or need enterprise-isolated registry structure.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Voice ready
Registry Root Threshold Split Gate gives TheoB a sane growth rule: small categories stay shared, growing categories become branches, heavy categories become dedicated registries, critical categories get root review, and enterprise-sensitive categories isolate early. No duplicates. No runaway registries. No million tiny kingdoms demanding a throne.
Registry Root Threshold Split Gate is active as a non-destructive threshold readiness gate under Synapse Infrastructure Hub. TheoB can define registry split tiers, split signals, split rules, future split candidate shape, and split receipt shape, but it cannot evaluate live registry splits, store split candidates, create registries, migrate records, merge registries, isolate enterprise branches, execute route consolidation, split visual clusters, or mutate production yet.
Keep category inside the general registry with tags, lightweight index markers, and shared provenance references.
Class: shared-generalThreshold: 0-1000 records, low query frequency, low sensitivity, low operational complexityDo not split too early. Tiny kingdoms become paperwork.Move category into a partitioned branch while preserving shared registry reference, canonical route, and provenance links.
Class: partitioned-branchThreshold: 1001-10000 records, rising query frequency, moderate category growth, or repeated route intersectionsPartition without orphaning context.Create a dedicated domain registry candidate with linked queue, receipt, storage partition, route consolidation, and provenance references.
Class: dedicated-domainThreshold: 10001-100000 records, high operational activity, frequent retrieval, or strong domain identityDedicated does not mean disconnected.Escalate category for root-level registry review with isolated queue, storage, receipt, and audit policy candidates.
Class: dedicated-root-reviewThreshold: 100000+ records, critical operational dependency, high routing complexity, or persistent cross-domain pressureRoot promotion requires founder/operator review.Escalate category for enterprise-isolated registry review regardless of record count.
Class: enterprise-isolated-reviewThreshold: enterprise tenant, regulated data, contractual separation, sensitive workflows, high-value private knowledge, or immediate compliance boundarySensitivity can outrank size.Detect when category record count crosses shared, partitioned, dedicated, root, or enterprise thresholds.
Use: size thresholdDetect when repeated query demand justifies branch or registry separation.
Use: runtime pressureDetect when route overlap, duplicate routes, or repeated intersections suggest registry separation or canonical consolidation.
Use: route consolidationDetect when storage load, retrieval cost, or indexing overhead suggests partitioning.
Use: storage optimizationDetect regulated, private, commercial, identity-sensitive, contractual, or enterprise-sensitive categories.
Use: sensitivity reviewDetect categories with dense provenance, many receipts, or long source trails needing dedicated structure.
Use: provenance managementDetect when visual cloud clusters become large enough to need quadrant or branch-level organization.
Use: visual compressionDetect enterprise tenants needing isolated registry roots, storage roots, queue roots, receipt rules, and audit posture.
Use: enterprise isolationDetect whether a proposed split already maps to a canonical route or existing branch.
Use: duplicate preventionShow registry split storage remains disabled.
Use: global lockCategories remain in the shared registry until record count, query frequency, sensitivity, route overlap, or operational pressure justifies separation.
Do not build a skyscraper for a lemonade stand.Crossing a threshold creates a split candidate, not an automatic registry mutation.
The gate recommends. It does not move the furniture.Before creating a new registry branch, check for canonical routes, existing branches, duplicate route classes, and shared synapses.
Consolidate roads before building cities.Any future split must preserve source trails, canonical route IDs, receipt links, review states, and inherited safeguards.
No split without ancestry.Enterprise-isolated registries require founder/operator review, retention policy, storage isolation, receipt posture, and access boundaries.
Enterprise isolation is architecture, not a checkbox.When categories split, visual dot identity, color signature, quadrant location, cluster identity, and microscope links must remain traceable.
A split should sharpen the picture, not erase the dots.This gate cannot create, store, migrate, split, merge, or isolate registries.
Readiness is not registry surgery.Registry Root Threshold Split Gate does not mutate production, registries, storage, queues, receipts, routes, visual clouds, enterprise branches, or agents.
No writes. No sync. No surprise.