Memory
GlassAgent knowledge plane = Work Engineering layer (SAP BOM + Routing mental model) Key shift: ex–mini-sphere is no longer "memory gadget" but the workspace's Work Engineering Database that holds engineered definitions and their evolution across the Discover–Design–Build–Operate–Improve–Innovate cycle. SAP analogues mapped to GlassAgent concepts: - Work Object = Material (BOM describes what the work product is made of: sub-objects, components, variants, cardinalities, acceptance criteria). - Ontology = Material master + BOM structure rules (type system, allowed item categories, BOM usages, multi-level constraints). - Canonical map = Union of all BOMs + Routings + Work Centers + configuration (complete master data defining the factory: work objects, processes, capabilities, policies, change history). - Workstations = Operations + Work Centers (each workstation is an operation with instructions/times/control keys, performed at a work center with capabilities, tools, logic type, capacity). - Contract = Operation specification + quality/inspection rules (input/output expectations, required components, evidence/confirmation requirements, challenge mechanisms). - Routing = Sequence of workstations under contracts (ordered operations for a work-object type, alternatives, reference operation sets, component allocation to operations). This is the missing first-class object in current notes. - Consequences = Costing, quality, planning, downstream impact (types: financial, compliance, reputational, operational; attached to objects/operations/contracts; drive approval/simulation/challenge rules). - Evidence = Confirmations, inspection results, change logs (operation confirmations, quality records, change documents for BOM/Routing changes, audit trails). - Work graph = BOM explosion + routing network + change documents (multi-level structures, alternative routings, explicit change/provenance edges). - Line Supervisor = Production planner / industrial engineer / Line Supervisor (designs BOMs/Routings, monitors production, handles exceptions, maintains intent). - Worker logic types = Work center categories / control keys (deterministic/probabilistic/possibilistic; manual/semi-auto/fully-auto; drives routing logic, oversight, cost). Open slots this highlights: - No explicit Routing object yet (sequence of workstations, alternatives, reference sets, component allocation). - No formal Work Object Definition schema (BOM header + items, variants, validity). - Component allocation to operations not yet modeled. - Consequence model not yet structured (types, attachments, rules). - Worker logic not yet a typed dimension of workstations/agents. - Canonical map schema still open (how all these objects are represented and related). - Minimum viable work object + contract not yet concretely defined. Design implication: the knowledge plane should store Work Object Definitions (BOM-like), Work Process Definitions (Routing-like), Workstation types (Work Center-like), Contracts (operation specs + evidence/inspection), Consequences, Evidence records, Ontology/meta-rules, and a change/supersession graph. GlassAgent's role in the iterative cycle is to discover/design/build/operate/improve/innovate these definitions as the workspace evolves. Next practical step: pick one concrete DocuClear use case and sketch a WorkObjectDefinition + WorkProcessDefinition (BOM + Routing) with consequence model and worker logic types, turning this reference architecture into an implementable schema.
Tags: glassagent, docuclear, sap, bom, routing, work-engineering, knowledge-plane, architecture, design, volatility:state, project:docuclear, kind:semantic — Source: mcp — 2026-09-05 05:23:34 UTC