@echelon-foundry/design-system 0.2.0 → 0.3.0-main.215.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Kevin Miller
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -71,6 +71,19 @@ clean consumer, and attaches the tarball to the GitHub release. npm publishing
 may be enabled through Trusted Publishing without changing the application
 contract.
 
+## Marketing sites
+
+Forma is the shared presentation system for every Echelon marketing website.
+The Echelon Foundry site is the visual reference, and each site consumes the
+same pinned artifacts:
+
+- the MarketingShell;
+- the brand-neutral marketing components and layouts;
+- the Echelon Marketing Theme.
+
+Start with `docs/MARKETING-SITES.md` and the reference fixture in
+`examples/echelon-marketing-site`.
+
 ## Branding and skins
 
 Forma supports versioned, scoped white-label presentation through Brand
@@ -80,3 +93,36 @@ domain authority.
 
 See [docs/BRANDING.md](docs/BRANDING.md) and
 [requirements/WHITE-LABEL-AND-SKINNING.md](requirements/WHITE-LABEL-AND-SKINNING.md).
+
+
+## Aegis fault presentation
+
+Forma includes a zero-runtime fault presentation family for Aegis `Presentation.T`: inline, notification, banner, blocking, summary, recovery actions, references, safe details, and diagnostic persistence status.
+
+Applications should map Aegis through the safe presentation model rather than bind a raw `Fault`. Recovery actions remain application/Ordo authorized and Limen-executed.
+
+See [docs/AEGIS-INTEGRATION.md](docs/AEGIS-INTEGRATION.md) and [requirements/AEGIS-FAULT-PRESENTATION.md](requirements/AEGIS-FAULT-PRESENTATION.md).
+
+
+## Object metadata and diagram/workflow presentation
+
+Forma now explicitly treats descriptive object metadata and diagram/workflow presentation as reusable cross-cutting capabilities.
+
+Objects may carry consumer-supplied metadata such as identifiers, descriptions, tags, owner/role, phase/category, status text, provenance/source references, and custom namespaced fields. Forma may present selected metadata, but the consuming application/profile remains the authority for values and meaning.
+
+Workflow/diagram items may also carry authored fill, border/stroke, accent, connector, and safe foreground colors. Color is presentation only. Semantic workflow type/status never derives from color, and meaningful distinctions must survive forced colors, grayscale, and backgrounds-disabled output.
+
+See `requirements/OBJECT-METADATA-AND-DIAGRAM-PRESENTATION.md`.
+
+## Figma
+
+Forma treats Figma as a design and developer-consumption surface, not as a
+second source of truth. Canonical tokens remain in
+`tokens/echelon.tokens.json`, canonical component anatomy remains in
+`patterns/*.html`, and `figma/component-contracts.json` provides complete,
+machine-readable coverage for the Figma library.
+
+See [docs/FIGMA.md](docs/FIGMA.md) for the variable, component, and Code Connect
+workflow. The public package also exposes `./tokens.json` and
+`./figma/components.json` for design tooling.
+