# PortaShape Synthesis Map

## Purpose

This map records how the uploaded materials were incorporated into the new PortaShape product canon. It also distinguishes canonical documents from preserved source material.

## Source-to-canon mapping

### `PortaShape.md`

Primary contributions:

- mapping, translation, and transmutation;
- visual source-to-destination relationships;
- settings versus options;
- website transfer and value-for-value reconstruction;
- snapshots, comparison, synchronization, preview, validation, provenance, security, versioning, unresolved values, reusable libraries, and `.posh` artifacts.

Canonical destinations:

- `docs/01-purpose-and-positioning.md`
- `docs/02-system-model-and-vocabulary.md`
- `docs/04-capabilities-and-modules.md`
- `docs/06-posh-artifact-model.md`
- `docs/08-use-cases-and-workflows.md`
- `docs/09-governance-security-and-validation.md`
- `spec/PORTASHAPE_0.1_CONCEPTUAL_SCHEMA.md`

Resolution applied:

The runtime interface is no longer described as a neighboring product. It is PortaShape’s operational surface, while mapping and transfer are relationship and execution capabilities over the same system model.

### `tuner.md`

Primary contributions:

- generated interfaces from data, code, schemas, styles, brand, motion, content, and runtime behavior;
- dynamic control surfaces;
- runtime feedback and tuning;
- pattern discovery;
- automatic, guided, manual, and adaptive generation;
- shared operational language across roles;
- connection, interpretation, control, composition, runtime, analysis, governance, and export layers.

Canonical destinations:

- `docs/01-purpose-and-positioning.md`
- `docs/02-system-model-and-vocabulary.md`
- `docs/03-product-experience.md`
- `docs/04-capabilities-and-modules.md`
- `docs/05-architecture.md`
- `docs/08-use-cases-and-workflows.md`

Resolution applied:

The “runtime interface” becomes PortaShape Explore, Shape, Runtime, and Surface capabilities. Its controls, observations, and patterns use the same identities and artifacts as mapping, comparison, and migration.

### `posh.posh`

Primary contributions:

- twelve conceptual examples progressing from direct copy to full website transfer;
- examples of settings, options, unit conversion, lookups, combine/split transforms, snapshots, CRM transfer, content migration, and complete runtime-assisted migration.

Canonical destinations:

- twelve individual JSON `.posh` files in `examples/`;
- example index in `examples/README.md`;
- conceptual format consolidation in `docs/06-posh-artifact-model.md` and `spec/PORTASHAPE_0.1_CONCEPTUAL_SCHEMA.md`.

Resolution applied:

The source catalog is preserved under `source-material/`, while its code blocks are extracted as machine-readable examples. The richer schema adds artifact kinds for surfaces, workflows, policies, runs, and libraries without invalidating the simple teaching profile.

### `htmxalpine04-main.zip`

Primary contributions:

- explicit state authority and DOM-writer doctrine;
- web-native progressive enhancement;
- native controls and routes;
- Alpine.js local interaction patterns;
- htmx request, swap, history, and multi-region patterns;
- semantic event contracts;
- lifecycle, accessibility, security, testing, and production discipline;
- onboarding curriculum, companion guides, source audit, and showcase ideas.

Canonical destinations:

- preserved corpus under `libraries/web-native-runtime/reference/`;
- product placement in `docs/07-web-runtime-library.md`;
- architectural integration in `docs/02-system-model-and-vocabulary.md`, `docs/03-product-experience.md`, `docs/05-architecture.md`, and `docs/09-governance-security-and-validation.md`;
- summarized reusable patterns in `libraries/web-native-runtime/PORTASHAPE_PATTERNS.md`.

Resolution applied:

The repository becomes a PortaShape library and reference renderer corpus rather than a separate workspace. Its technology-specific version baseline remains owned by its own manifest.

## Canonical versus reference documents

### Canonical

The top-level README, numbered documents, conceptual schema, example index, library wrapper, and roadmap define the new unified product story.

### Reference

Files under `source-material/` and `libraries/web-native-runtime/reference/` preserve the uploaded sources. They provide detail, evidence, examples, and implementation education but do not override the unified terminology in the canon.

## Major conceptual reconciliations

1. **One product:** runtime control, mapping, migration, comparison, and libraries operate on one system graph.
2. **One purpose:** make digital systems visible, operable, and portable.
3. **One artifact family:** `.posh` stores not only mappings but systems, surfaces, transforms, workflows, policies, libraries, snapshots, and runs.
4. **One authority model:** settings, options, runtime state, source truth, proposals, and previews remain distinct.
5. **One workspace:** Explore, Shape, Map, Run, Compare, and Library are lenses, not isolated compartments.
6. **One implementation library placement:** Alpine.js + htmx is a web-native runtime library under PortaShape, not the product boundary.