@tiinex/core

@tiinex/core is the shared host-neutral implementation core behind Tiinex consumers. It implements portable artifact interpretation, schema/runtime contracts, validation, lineage, continuity, grounding, Handoff/package mechanics, deterministic projections, and companion-resource resolution without assigning canonical semantic authority to a UI host or repository location.

Canonical schema meaning remains in Tiinex Docs. Core implements those contracts. Business retains organizational prioritization and human gates. Site, VS Code, Chrome, CLI and other consumers are hosts rather than independent semantic engines.

Public boundaries

• @tiinex/core / @tiinex/core/browser — browser-safe data projection and companion-resource contracts.
• @tiinex/core/node — the browser-safe surface plus portable Tooling for Node hosts.

The browser entrypoint does not import Node built-ins. Package consumers must not import undocumented internal paths.

Companion resources

Companion lookup is provider-oriented. Artifact-local Workspace material, deployment overrides, Verse package defaults and lower-level defaults can participate without making physical repository placement semantic authority. Specificity is resolved before provider precedence; unresolved same-level single-value conflicts fail closed.

Layout

Source paths intentionally follow the same src/... conventions used by other Tiinex repositories where the concepts match. npm distribution preserves this source layout rather than inventing a second directory vocabulary.

Current implementation frontier

@tiinex/core is a published package boundary; package publication does not by itself establish browser/product acceptance or semantic authority. App/Site/Verse integration remains separately qualified by those consumers.

The explicit package export map exposes the shared module paths used by App. These preserve the mirrored layout, not a second implementation. tools/tiinex-portable.mjs remains a transitional compatibility entrypoint while dedicated CLI/Interop hosts are stabilized. See docs/ARCHITECTURE-BOUNDARIES.md for the carrier-bootstrap, schema-material and external-Interop split.

Application data is a declared-data projection: parsing and exact reference resolution are not schema validation, integrity verification or authority qualification. Missing Parent evidence remains unresolved. Companion byte access belongs to registered host readers, not automatic filesystem or network permissions.

npm release frontier

Master-only automatic versioning/publication is implemented through the Core Node release helper. See docs/NPM-PUBLISH.md. OIDC/Trusted Publisher configuration is an external repository/package setting and remains separate from source qualification.