Architecture Commit Glossary
A practical glossary for the LumenVision / OneVizion Architecture Commit conversation. These definitions explain how each term is being used in this project, so the team can discuss scope, ownership, integrations, and risks with the same vocabulary.
Process And Positioning
Architecture Commit
Formal approval checkpoint that moves LumenVision from concept into solutioning and development funding.
How to use it: Use it to align scope, value, architecture artifacts, open decisions, and risk before build work accelerates.
LumenVision / OneVizion
The proposed workflow, planning, orchestration, and visibility layer for Lumen network implementation work.
How to use it: Position it as the work surface and coordination layer, not as the owner of every business object.
Source Of Truth
The authoritative system or team that owns a business object and is trusted to update it.
How to use it: A key commit question is which system owns each object: order, task, site, BOM, inventory, status, date, and document.
System Of Record Matrix
A decision artifact that maps each business object to an authoritative owner, consumers, confidence level, and open questions.
How to use it: Use it to prevent duplicate ownership and unclear write-back behavior.
Customer POV
The customer-facing recommendation narrative: what we understand, what problem Lumen is solving, and what solution path we recommend.
How to use it: This is the best starting point for executive or customer discussion.
Release 1 Anchor
The first bounded workflow or use case used to prove the target architecture.
How to use it: Possible anchors include Service Delivery, SiteTracker exit, Network Grooms, RNI, Waves, or Dark Fiber.
Service Delivery
A major candidate workflow area for Release 1 and architecture commit scope.
How to use it: Lumen needs to decide priority and path forward for the Service Delivery module.
SiteTracker Exit
Migration or replacement path away from SiteTracker for selected project/workflow scope.
How to use it: Treat it as both a deadline migration problem and a future workflow transformation decision.
Network Grooms
Network grooming workflow area discussed as one of the next scope decisions.
How to use it: Clarify owner, release priority, integration points, and whether it belongs in Release 1.
Systems And Domains
SOM 2.0 / BlueSteel
Service order management flow that sits between product order sources and downstream implementation workflows.
How to use it: Important dependency for service-order events, date publishing, Kafka headers, and workflow generation.
Salesforce / NEO
Product order and sales/order-entry source area.
How to use it: Do not let LumenVision casually become product-order authority unless Lumen explicitly changes ownership.
BPI
Network order or design execution system area referenced in the target workflow.
How to use it: LumenVision may create, request, monitor, or receive status from BPI depending on agreed integration contract.
BluePlanet / VoltRon
Target inventory and network design/inventory direction.
How to use it: Likely authoritative for network inventory, but interim ownership and write-back rules need confirmation.
GLM / 3GIS
Location, route, site, and survey-related systems.
How to use it: Important for planning requests, route/span objects, and network opportunity data.
SAP S/4HANA
Material master, BOM, procurement, vendor sourcing, capital, and finance-related system.
How to use it: Architecture commit must define what LumenVision reads, writes, or references for material and funding workflows.
BOM
Bill of Materials: structured list of required parts/materials for design or build.
How to use it: BOM standardization matters because material mismatch creates sourcing and execution risk.
Material Master
Authoritative standardized material and part-number data, likely owned in SAP.
How to use it: Needed so LumenVision, engineering, sourcing, and procurement speak the same material language.
Kafka / CFKA
Event backbone for state changes, traceability, replay, dead-letter handling, and integration between systems.
How to use it: Treat Kafka headers and contracts as architecture dependencies, not low-level implementation details.
Integration And Data
Kafka 2.0 Headers
Traceability and correlation metadata required for observability across event flows.
How to use it: Should be a commit blocker if SOM 2.0 and downstream consumers depend on them.
DLQ
Dead Letter Queue: event handling pattern for failed or invalid messages.
How to use it: Needs an operating model: who monitors, retries, resolves, and reports integration failures.
Data Hub
Stitched read view and integration/reporting consumer.
How to use it: It can aggregate state, but should not automatically be treated as update authority.
WFM / SFS / Flight Deck
Field execution and task platforms used by different personas or migration states.
How to use it: Define which tasks remain there versus which tasks move to or are displayed by LumenVision.
ByFrost
Single-pane/context package concept for field or operational users.
How to use it: Clarify whether it is an aggregator only or whether any operational authority lives there.
GCR / ServiceNow
Change notification/ticketing area with possible future ServiceNow direction.
How to use it: Define whether LumenVision triggers, monitors, or simply references change notifications.
ADO / AI Agents
AI-assisted decision orchestration and workflow support.
How to use it: Keep actions human-supervised until lineage, audit, rollback, replay, and guardrails are proven.
RAG
Retrieval-Augmented Generation: AI pattern that answers using controlled source material.
How to use it: Useful for document, rule, permitting, and operational guidance, but needs source governance.
Human-Supervised AI
AI recommends or prepares an action, but a person reviews or approves before execution.
How to use it: This is the safer Architecture Commit position for early AI scope.
Integration Contract
Agreed data, event, API, ownership, error, and retry behavior between systems.
How to use it: Every high-priority integration should have one before development commitments become firm.
Write-Back
When LumenVision or another consumer updates a source system, not just reads from it.
How to use it: Write-back needs owner approval, validation, rollback, replay, and audit rules.
Context Package
A bundle of order, task, site, inventory, document, and status context passed to a user or downstream system.
How to use it: Useful for reducing swivel-chair work across LumenVision, ByFrost, and field systems.
Program Terms And Acronyms
MVP
Minimum viable product or first usable release scope.
How to use it: For this program, MVP should prove priority workflow, ownership, integration, and value without overclaiming universal scope.
BAU
Business as usual: current operations that must continue during transformation.
How to use it: Architecture must protect BAU while moving target workflows into LumenVision.
FT3
A named Lumen workstream or program term seen in the meeting action items/session notes.
How to use it: Needs confirmation from Lumen on scope, owner, and relationship to SiteTracker exit and BAU work.
Project Helix
Transformation/migration program context tied to workflow and legacy exit decisions.
How to use it: Use it as a dependency lens when discussing SiteTracker, Netbuild, Armor, and future workflow shape.
NSA
Network Systems Architecture or related Lumen architecture context, based on work item references.
How to use it: Confirm the exact internal meaning with Lumen before using the acronym externally.