Enterprise Architecture
Preserving recognisable business intent as requirements, systems, decisions, and delivery forms change.
Read the application →Applications
LUX143 is a research field, but its principles apply wherever meaning, identity, intent, or evidence must remain recognisable through change.
Applications translate the field into domains, without turning it into a services catalogue.
Translation layer
The applications layer helps readers begin from their own context: enterprise change, AI governance, heritage evidence, institutional memory, or research partnership.
Each page asks who the work is useful for, what problem becomes readable, which LUX143 principle applies, which renderer demonstrates it, and what outcome the audience can expect.
Domains
These are not service pages. They are use-case translations: practical ways to understand how recognisability, traceability, orientation, and continuity matter in different fields.
Preserving recognisable business intent as requirements, systems, decisions, and delivery forms change.
Read the application →Preserving human orientation, accountability, and traceability when automated systems accelerate interpretation.
Read the application →Preserving recognisable heritage when objects, records, routes, memories, and public stories change carrier.
Read the application →Planned translation for collections, provenance, interpretive uncertainty, and public memory.
View planned page →Planned translation for research partners working with evidence, methods, publication boundaries, and field formation.
View planned page →Context
Start here if your question is practical. Read the ecosystem architecture only when you need to understand how the public renderers fit together as one field.
The canonical map of LUX143 public renderers and the continuity problem they share.
Read the ecosystem architecture →