Built Systems and Morphogenic Systems

Built Systems and Morphogenic Systems introduces a conceptual framework for distinguishing predetermined information structures from governed systems capable of adapting representations, relations, context and permitted behaviour. A Built System is organized primarily through schemas, categories, relationships, workflows and transition rules configured in advance. A Morphogenic System is defined as a governed information environment capable of adapting selected information structures while preserving explicit continuity of identity, evidence, boundaries, causality and contradiction. The paper identifies six potential objects of adaptation: representation, relation, context, evidence state, permitted behaviour and interface contract. It proposes five continuity requirements: identity continuity, evidence continuity, boundary continuity, causal continuity and contradiction visibility. It also introduces information-condition gradients, local interaction rules, evidence classifications, evaluator relationships, failure conditions and a versioned Morphogenic profile declaration. The term "morphogenic" does not mean unrestricted autonomy, self-authorization or uncontrolled machine learning. A system does not become morphogenic merely because it uses artificial intelligence, changes state, stores memory, updates a schema or modifies an output. Morphogenic claims must be scoped to a declared profile and supported by observable evidence. The framework is positioned as complementary to established work on adaptive software, schema evolution, temporal and event-based systems, provenance and governed AI. It does not prescribe a particular database, graph, model, protocol, control loop, algorithm, scoring method or deployment architecture. This is Paper 1 of the Morphogenic Systems Research Series. Subsequent papers address black-box behavioural conformance, machine-entity boundary interfaces and information-architecture risk in high-accountability environments. Publication status: Independent technical report. The work is conceptual and implementation-neutral. It is not a technical standard, certification scheme, regulatory determination, security assessment, financial recommendation or claim of independent validation.