Skip to content

Unversioned binding handoff for the app

Eve requested removal of template-content, binding-schema and source-adapter revision numbers. This change belongs to simulation-templates PR #224 and needs matching app work. It is not an update to dependency installation. This handoff is for Eve to review and pass to the app chat; it has not been sent there.

Origin authoring

All eight Config declaration blocks now identify only the analysis and engine:

# <TEMPLATE_METADATA>
template = {'id': 'zapfdtd_3d', 'engine': 'fdtd'}
sources = ['gds', 'gsch_layout', 'py']
requirements = {'gsim': '>=0.8.0'}  # optional; package requirements stay
# </TEMPLATE_METADATA>

There is no authored version, template_version, binding/schema revision or adapter revision. Keep inline USER inputs, AUTO authority and source-route support unchanged. No new author field replaces the deleted fields.

Exact internal changes

Previous reference name Current reference name
auto_user_tokens_v3 auto_user_tokens
gdsfactory_component_v1 gdsfactory_component
python_factory_component_v2 python_factory_component
gds_component_v1 gds_component
gsch_layout_component_lvs_v1 gsch_layout_component_lvs
scripts/contracts/v3/ scripts/contracts/

The registered adapter files use the corresponding unnumbered basenames. The unregistered, superseded Python factory loader was removed. There is one current Python loader, preserving the exact import-root/module-path checks and invocation behavior. Source formats and output types still have names; they have no revision suffixes or numbered compatibility dispatch.

Remove the following fields from current binding structures and their producers, consumers, fixtures and specs:

  • Expanded origin projection: schema_version, authoring_version, template_version.
  • Binding declarations: version; the reference projection now contains slots and optional relations only. The app can retain its smaller existing projection.
  • Reference binding context: schema_version; validate the current structure directly, rejecting obsolete version fields as unknown fields.
  • Kind registry and adapter registry: top-level version.
  • Acquisition descriptor: registry_version, declaration_schema_version, context_schema_version, provenance_schema_version, adapter_registry_version.
  • Descriptor dependency records: version; retain path and sha256.

The descriptor retains binding_contract, dependencies and canonical_sha256. It is an in-memory reference-tooling snapshot, never a delivered sidecar. The app should use its existing retained bytes, hashes and compiled handlers; it does not need to import the reference JSON schemas or add this descriptor to origins.

App implementation checklist

  1. Finish removing template_version from compact parsing, catalog/RPC records, generation and example/fixture/spec data. Regenerate affected API types through the normal project workflow.
  2. In crates/gfp-server/src/notebook/compact.rs, rename the three registered adapter IDs and include_str! paths. Move the compiled .py.in adapter sources from contracts/v3/source_adapters/ to contracts/source_adapters/, using the unnumbered basenames above. Preserve their implementation and provenance hashes.
  3. In compact.rs and planning.rs, remove the generated declaration version and the check requiring 3. Keep strict allowed fields, basic type checks, source/picker authority and bounds. Update construction sites in inline-input, generation, plan-context and planning/review tests. Do not port the reference tool's historical richer schema features back into the lean app implementation.
  4. Audit generated notebook stamps, retained plans, catalog compatibility and publication checks for numbered binding/adapter fields or IDs. Use the current app-owned handler and validate actual shape/capability. Unknown or obsolete structures fail clearly; there is no version negotiation or automatic fallback.
  5. Update binding conformance fixtures, names/paths, integration scripts and specs that depend on the old labels. Reference Python helpers and tests are now unnumbered (test_generic_bindings.py, test_build_templates.py); reference helper imports now use read_json, binding_records, resolve, bind_expression, compose_origin and descriptor instead of their numbered predecessors. The source format is still validated even though its revision number is gone.
  6. Prove versionless discovery, all three geometry routes, inline inputs and portable alternatives, unchanged authority/escaping, and fresh notebook creation. Retain tests rejecting obsolete fields, changed acquired notebook bytes, changed source/adapter bytes under the same name, unsupported routes and partial publish. Run the app's own native/API/UI checks; reference tests are not app acceptance.

The separate persisted association-record format in associations.rs also has a schema_version. That is an app storage/migration protocol, not the removed binding schema declaration. Do not silently delete its validation or hash-domain markers as a string-cleanup exercise. Handle that separately if Eve requests removing storage-format versions. Keep source/project/catalog freshness hashes.

Delivery and dependencies

The archive layout is unchanged: nested authoring tree, flat canonical .ipynb files at the ZIP root, no sidecars/shared implementations. The templates PR may merge before DataLab PR #4034. Upload stays disabled until its endpoint is deployed; this change does not enable publishing. Package requirements remain PEP 440 constraints. Honor them through the planned uv-native project dependency workflow; discuss that design with Eve before implementing installation, repair or an additional resolver. External standards such as Jupyter nbformat/nbformat_minor and JSON Schema dialect URIs remain.