@volter/twin-catalog 0.2.2

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,148 @@
+# Twin catalog
+
+The catalog admits and distributes twin packages from independent publishers. It prepares evidence for moderators;
+people decide what merges. The platform and pack repositories have their own release cycles. The
+[process contract](docs/process.md) defines the boundaries, states and acceptance cases.
+
+## Submit a release
+
+Register a source with a pull request adding one entry to `sources.json`:
+
+```json
+{ "name": "example-team", "repository": "example/twins", "scope": "@example", "official": false, "protocol": "3", "workflow": "release.yml" }
+```
+
+The CLI can prepare that addition in your catalog fork:
+
+```sh
+twin-catalog register --source example-team --source-repository example/twins --scope @example
+```
+
+It writes `sources.json` only. An installed CLI outside a fork writes `registration/sources.json`; use `--out` for
+another output path. Open a separate source-registration PR before submitting releases. A matching existing source
+is idempotent; conflicting registration data is refused.
+
+After registration merges, publish a package from that public repository with npm provenance. Its package.json names
+the registered repository; its generated pack facts name the vendor it simulates. A package may have any scoped npm
+name. Its artifact includes the source, spec and journeys required by the released Protocol 3 standard. Build against
+the published SDK and standard; no platform checkout is needed by this catalog.
+
+In a fork of this catalog, create the submission with its released CLI or this identical repository command:
+
+```sh
+node bin/twin-catalog.mjs submit --source example-team --vendor stripe --package @example/stripe-simulator --version 1.2.3
+```
+
+Open a PR adding only the generated `submissions/<sha256>.json`. The CLI writes data only. Automation downloads the
+exact artifact, verifies its integrity and provenance, installs dependencies without scripts, runs the standard in
+an offline container and a World, and updates one feedback comment. Download the JSON report and diagnostics from
+the workflow artifacts; admitted reports also have a durable evidence release and an index-package copy. Code fixes require a new published version and updated submission filename. Do not edit the
+index, policy or source registration as part of a release submission.
+
+Passing automation means ready for a maintainer decision. Untrusted-account submissions require moderator review
+of the exact head before merge. Direct trusted-account submissions, including forks, and eligible internal publisher
+submissions permit an authorized maintainer merge without a separate review. The catalog does not approve or merge itself. A rejection is a closed PR with a reason. Moderators are named
+in `.github/CODEOWNERS`.
+
+## Consume the index
+
+An unassessed historical release may be submitted with `--reassess`; its file belongs in `reassessments/` and goes
+through the same checks and moderation. A version without its original provenance must be followed by a new release.
+
+`@volter/twin-catalog` carries `sources.json`, `vendors/`, `recommendations.json`, `revocations.json` and `catalog.json`.
+Vendor and package identities are separate. Multiple implementations remain visible; recommendations select a default
+package when necessary. Stable approved versions are selected within that package. World pins do not move. Historical
+index entries without an assessment are identified as unassessed.
+
+```sh
+node bin/twin-catalog.mjs check
+node bin/twin-catalog.mjs defaults
+node bin/twin-catalog.mjs build --out /tmp/new-catalog-output
+```
+
+The build requires committed admission records and a new output directory. It generates data without importing packs.
+The website and hosted runtime consume this artifact independently; publishing it does not deploy either.
+
+For discovery, use the JSON-only reader against an installed index:
+
+```sh
+twin-catalog browse --root ./node_modules/@volter/twin-catalog
+twin-catalog browse --root ./node_modules/@volter/twin-catalog --vendor stripe
+```
+
+The `./browse` library export provides the same projection for a website build or another consumer:
+
+```js
+import { browse } from '@volter/twin-catalog/browse';
+const catalog = browse('./node_modules/@volter/twin-catalog');
+```
+
+Every implementation and recorded release remains visible. An ambiguous vendor has `selection.state: "choice-required"`.
+Filtering a package does not change the vendor's default. Revocation, selectability and assessment availability are
+separate fields. Bound report measurements retain their original scope; absent measurements are `null`. The reader
+checks snapshot and report digests without importing packs or reading Git history. `snapshot.integrity` is `null`
+unless the caller supplies retained installation evidence; the reader does not verify the package tarball. See
+[the read contract](docs/process.md#read-the-published-catalog).
+
+## Operate admission
+
+The [operator procedure](docs/operations.md) covers failed phases, immutable retries, revocation and credential roles.
+
+`policy.json` pins released evaluator versions and the registry. Policy changes are separate moderator-reviewed PRs.
+The evaluator requires Docker on Linux with an x86-64 runner (the pinned Bun binary is linux-x64). Reports record the actual image identity and dependency lock, PR head/base,
+and policy identity. Docker network isolation applies to evaluation; preparation downloads npm packages and
+attestations. No credentials enter either container.
+
+With a repository administration token in `GH_TOKEN`, inspect the proposed branch rule:
+
+```sh
+node bin/twin-catalog.mjs configure --repository volter-ai/twin-catalog-open
+```
+
+An authorized operator adds `--apply` to require current-head readiness, stale-review dismissal, code-owner approval,
+last-push approval and administrator enforcement, and enable Actions. CODEOWNERS initially names the existing
+catalog administrator, `@yueranyuan`; add other authorized people or teams there through moderator review.
+Ordinary commands never modify these settings. Source and catalog repositories must be public for npm provenance;
+publication needs npm trusted publishing or the workflow's scoped `NPM_TOKEN`. These are activation prerequisites,
+not changes performed by implementing this process.
+
+`policy.reviewBypassUsers` names maintainers allowed to merge direct trusted-account and internal changes without
+a separate review. `policy.trustedAccounts` binds direct PR authors by GitHub numeric ID, exact login and account
+type, including contributions from forks. `policy.internalRepositories` separately lists registered pack repositories
+eligible for the internal publisher path. Untrusted accounts still need human review; all admissions need verified
+provenance and current-head readiness. The [process contract](docs/process.md) defines these admission paths.
+`policy.internalBotAuthors` binds each trusted publisher bot by GitHub user ID and exact login. It grants no
+exception without the internal source, same-catalog PR and authorized maintainer merge.
+
+The publication workflow uses a GitHub App with repository administration read, contents read, checks read and
+pull requests read. Install it only on the catalog repositories, set repository variable `CATALOG_READ_APP_CLIENT_ID`
+and secret `CATALOG_READ_APP_PRIVATE_KEY`, and keep its private key out of source and diagnostic output. Each job
+mints a short-lived token limited to its own repository; the action revokes it after the job. Existing deployments
+may supply an equivalent scoped `CATALOG_READ_TOKEN`. No administration write permission is needed by publication.
+Missing policy access refuses publication. Publisher CI can run `twin-catalog propose --from <submission-directory> --send` with its
+separate catalog PR token; that command opens idempotent submission PRs and never approves or merges them.
+
+Workflow dispatch with a PR number reruns readiness after an infrastructure failure. Publication dispatch retries
+the same source commit: its version derives from first-parent history, and an already published matching identity is
+reused. Force pushes are forbidden. A conflicting identity fails. `publish` verifies branch protection and admission
+PRs before using npm credentials. Append a `package`, `version`, and `reason` entry to `revocations.json` to remove a
+release from future selection; existing World pins are preserved.
+
+Set `CATALOG_PUBLISH_ENABLED=true` only after readiness verification and moderator setup.
+
+Volter's pack release workflow stays inactive while its source repository is private, as required by npm provenance.
+Its trusted release workflow uses `CATALOG_PR_APP_CLIENT_ID` and `CATALOG_PR_APP_PRIVATE_KEY` in the pack repository
+to mint a short-lived catalog contents/pull-request write token, without administration. Install that separate App
+only on the target catalogs. Existing scoped `CATALOG_PR_TOKEN` configuration remains supported. Outside publishers
+use their own GitHub accounts/forks, never Volter's App key. Source visibility exposes Git history and remains an
+explicit owner decision.
+
+[Build in your own repository](docs/contributing.md) uses the released tools.
+
+Browser pages are separate work. JSON reports distinguish quick replay from full admission conformance; unmeasured
+DOM, line and state coverage remain explicit. Readiness artifacts are evidence, not a fidelity guarantee.
+
+A publisher that has just completed npm upload can use `submit --confirm-published` to wait for its exact
+version metadata before opening a PR. Only HTTP 404 is retried, every 15 seconds for at most ten minutes, based
+on [the registry measurement](docs/measurements/registry-confirmation.json). Other errors and identity mismatches
+fail immediately. This option performs registry reads only; it never uploads or evaluates a package.

package/bin/twin-catalog.mjs

@@ -0,0 +1,79 @@
+#!/usr/bin/env node
+import { existsSync, readFileSync } from 'node:fs';
+import { dirname, join, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { loadIndex, defaults, read, write, requireThat, stable, submissionId, validateSubmission } from '../lib/model.mjs';
+import { metadata } from '../lib/registry.mjs';
+import { GitHub } from '../lib/github.mjs';
+import { assessPullRequest, configure } from '../lib/automation.mjs';
+import { build, builtIndex, publish, verifyAdmission } from '../lib/publication.mjs';
+import { persistEvidence } from '../lib/evidence.mjs';
+import { propose } from '../lib/propose.mjs';
+import { browse } from '../lib/browse.mjs';
+import { register } from '../lib/register.mjs';
+
+const [command, ...args] = process.argv.slice(2);
+const arg = (name, fallback) => { const at = args.indexOf(`--${name}`); if (at < 0) return fallback; requireThat(args[at + 1] && !args[at + 1].startsWith('--'), `--${name} needs a value`); return args[at + 1]; };
+const root = resolve(arg('root', process.cwd()));
+const installed = resolve(dirname(fileURLToPath(import.meta.url)), '..');
+const policy = () => read(join(existsSync(join(root, 'policy.json')) ? root : installed, 'policy.json'));
+const github = () => new GitHub(arg('repository', process.env.GITHUB_REPOSITORY ?? 'volter-ai/twin-catalog-open'), process.env.GH_TOKEN ?? process.env.GITHUB_TOKEN);
+try {
+  let result;
+  switch (command) {
+    case 'browse': {
+      const indexRoot = args.includes('--root') || existsSync(join(root, 'catalog.json')) ? root : installed;
+      result = browse(indexRoot, { vendor: arg('vendor'), package: arg('package'), integrity: arg('integrity', null) });
+      break;
+    }
+    case 'register': {
+      const fork = existsSync(join(root, 'sources.json'));
+      const indexRoot = fork ? root : installed;
+      result = register(read(join(indexRoot, 'sources.json')), {
+        name: arg('source'), repository: arg('source-repository'), scope: arg('scope'),
+        official: args.includes('--official'), protocol: '3', workflow: arg('workflow', 'release.yml')
+      }, resolve(arg('out', join(root, fork ? 'sources.json' : 'registration/sources.json'))));
+      break;
+    }
+    case 'submit': {
+      const indexRoot = existsSync(join(root, 'sources.json')) ? root : installed;
+      const p = policy();
+      const doc = await metadata(arg('package'), arg('version'), p.registry, fetch, args.includes('--confirm-published') ? {} : undefined);
+      const submission = { schemaVersion: 1, source: arg('source'), vendor: arg('vendor'), package: doc.name, version: doc.version, integrity: doc.dist?.integrity };
+      validateSubmission(submission, loadIndex(indexRoot).sources);
+      const file = resolve(arg('out', join(resolve(arg('out-dir', join(root, args.includes('--reassess') ? 'reassessments' : 'submissions'))), `${submissionId(submission)}.json`)));
+      requireThat(file.endsWith(`/${submissionId(submission)}.json`), 'output must be named for the submission identity');
+      if (existsSync(file)) requireThat(stable(read(file)) === stable(submission), 'submission output already exists with different content');
+      write(file, submission);
+      result = { file, submission, next: 'Open a pull request adding only this submission file to the catalog. No publication or PR was performed.' };
+      break;
+    }
+    case 'defaults': result = defaults(builtIndex(existsSync(join(root, 'sources.json')) ? root : installed)); break;
+    case 'check': result = { valid: Boolean(builtIndex(existsSync(join(root, 'sources.json')) ? root : installed)) }; break;
+    case 'assess-pr': {
+      const event = process.env.GITHUB_EVENT_PATH ? read(process.env.GITHUB_EVENT_PATH) : {};
+      result = await assessPullRequest(root, github(), Number(arg('pr', process.env.CATALOG_PR ?? event.pull_request?.number)), resolve(arg('out', 'assessment/report.json')));
+      if (result.status !== 'ready') process.exitCode = 1;
+      break;
+    }
+    case 'configure': result = await configure(github(), args.includes('--apply'), policy().reviewBypassUsers ?? []); break;
+    case 'propose': {
+      requireThat(args.includes('--send'), 'propose opens GitHub PRs; pass --send for this explicit publisher action');
+      result = await propose(github(), resolve(arg('from', args.includes('--reassess') ? 'reassessments' : 'submissions')), args.includes('--reassess'));
+      break;
+    }
+    case 'build': result = build(root, resolve(arg('out', 'dist'))); break;
+    case 'publish': {
+      const client = github();
+      const policyClient = process.env.CATALOG_READ_TOKEN ? new GitHub(client.repository, process.env.CATALOG_READ_TOKEN) : client;
+      const proofs = await verifyAdmission(root, client, policyClient);
+      const evidence = await persistEvidence(proofs, client);
+      const output = resolve(arg('out', 'dist'));
+      build(root, output, evidence);
+      result = await publish(output, policy().registry);
+      break;
+    }
+    default: throw new Error('usage: twin-catalog register --source <id> --source-repository <owner/repo> --scope <@scope> [--out <sources.json>] | submit --source <id> --vendor <vendor> --package <@scope/name> --version <exact> | browse [--root <installed-index>] [--vendor <vendor>] [--package <@scope/name>] | assess-pr --pr <number> | check | defaults | build --out <new-directory> | publish | configure [--apply] | propose --from <submission-directory> --send');
+  }
+  console.log(JSON.stringify(result, null, 2));
+} catch (error) { console.error(`twin-catalog: ${error.message ?? error}`); process.exitCode = 1; }

package/catalog.json

@@ -0,0 +1,6 @@
+{
+  "schemaVersion": 1,
+  "sourceCommit": "646cb5db50f24248f177e1fab1ccdeb681e7005b",
+  "digest": "1c1ad9dfb2fd6cba0923988b3a1f17c6da892efc3a5ec36f230a91c88a437ff6",
+  "versions": []
+}

package/docs/contributing.md

@@ -0,0 +1,91 @@
+# Publish from your own repository
+
+The catalog accepts independently named packages from independently owned repositories. Use the released standard,
+not scripts from a platform checkout. Read the [process](process.md) for identity, assessment and moderator authority.
+
+## Build a pack
+
+Install Bun at the catalog policy's version and the public `@volter/world-core`, `@volter/world-runtime` and
+`@volter/twin-standard` versions in `policy.json`. Install TypeScript and its Node/Bun types as development dependencies.
+Keep the package directory named for the vendor; its npm package name is independent.
+
+```sh
+bunx --bun twin-standard create stripe --init stripe --package @example/payments
+```
+
+The generated files contain explicit fill markers. Author the vendored spec and its provenance, demand, manifest,
+stored resource states, decision table, handlers and customer journey in the standard's required order. The package
+README describes its vendor surface, refusals and limits. Declare your own public GitHub repository and license in
+package.json. Complete source requirements before derivation:
+
+```sh
+bunx --bun twin-standard check-sources stripe
+bunx --bun twin-standard derive stripe
+bunx --bun twin-standard create stripe --index
+bunx --bun twin-standard facts stripe
+```
+
+The command has the same handler-map and kernel contract as Volter's own wrapper. The generated facts belong in the
+package artifact; keep source, spec, journeys and required fixtures there too. Publish compiled JavaScript for Node
+consumers while retaining the TypeScript source the pinned standard reads. Use TypeScript's
+`rewriteRelativeImportExtensions`, copy generated JSON alongside emitted modules, and point the package export and
+bin at their compiled entrypoints. A `files` list includes `src`, `dist`, `generated`, `spec`, `journeys`, README and
+LICENSE. A build and `npm pack --dry-run` must show those paths; no platform-specific prepack script is required.
+
+## Assess before submitting
+
+Walk the life's journeys while implementing. For the final assessment, run the released standard through a World:
+
+Create `assessment.world.config.json`:
+
+```json
+{ "id": "pack-assessment", "services": [], "network": { "egress": [] } }
+```
+
+```sh
+volter-world run assessment.world.config.json --root . --env-out /tmp/new-assessment.env --owner pack-assessment -- bunx --bun twin-standard assess stripe --browser --out assessment.json
+```
+
+The assessment config has no vendor services; the standard creates fresh in-memory World state for each journey.
+For an HTTP browser target, use Linux, install Playwright at the catalog policy version and its Chromium binary,
+and install `libfaketime` (Debian/Ubuntu: `sudo apt-get install libfaketime`). The browser process uses the World
+clock for native cookie expiry, at one-second precision; JavaScript time retains millisecond precision. Authors on
+other platforms can omit `--browser` for in-process assessment; catalog Actions supplies the browser target. The report
+separates declared served/gap counts, operations actually exercised, deterministic replay, conformance and Chromium
+results. It does not measure DOM interactions, line coverage, real-vendor parity or every possible state transition.
+
+Local assessment helps authors; it does not replace the independent catalog assessment of the published tarball.
+Linux catalog preparation disables installation scripts. A dependency that requires a build cannot depend on its
+postinstall having run there: distribute the needed portable build or choose supported dependencies.
+
+## Register and publish
+
+Register your public repository, npm scope and release workflow in a separate authorized `sources.json` PR; untrusted accounts need moderator review.
+In your catalog fork, prepare the one-source change using the catalog CLI:
+
+```sh
+twin-catalog register --source example-team --source-repository example/twins --scope @example --workflow release.yml
+```
+
+The command prepares data only and refuses conflicting registrations. Outside a fork it writes `registration/sources.json`;
+copy that file into your fork and open the separate PR. Registration does not authorize a release or grant maintainer status.
+
+Pin your own dependencies and commit the lock. Your workflow runs on GitHub-hosted Linux with `id-token: write`,
+builds your artifact, and uses npm trusted publishing or your own scoped npm credential:
+
+```sh
+npm publish --ignore-scripts --access public --provenance
+```
+
+The artifact's repository URL matches the registered repository; the signing workflow filename matches registration.
+Publishing does not admit a release. After source registration has merged, use the catalog CLI from a catalog fork:
+
+```sh
+twin-catalog submit --source example-team --vendor stripe --package @example/payments --version 1.2.3
+```
+
+Open a PR adding only its generated submission. The Actions job checks the registry artifact at the exact integrity,
+using catalog policy and released tools, then posts readiness evidence. Untrusted accounts need moderator review;
+directly trusted accounts need no separate review. The [process contract](process.md) defines account trust and
+maintainer authority. Fixes need a new immutable release; infrastructure failures can be retried. Authorized
+maintainers merge; the publisher and catalog workflows do not.

package/docs/measurements/installation-metadata.json

@@ -0,0 +1,14 @@
+{
+  "mode": "GitHub Actions preparation failure and exact-version confirmation",
+  "sourceCommit": "6b1eeacaf7f629db2985d213f52fdcf0013dc045",
+  "assessmentBase": "31af65e30b619cf47fd3387c6de97611effe56c0",
+  "workflowRun": 37350037621,
+  "failedAttempt": 1,
+  "successfulAttempt": 2,
+  "command": "node bin/twin-catalog.mjs assess-pr --out assessment/report.json; npm install --ignore-scripts --no-audit --no-fund --registry https://registry.npmjs.org",
+  "concurrentWork": "exact-version metadata and artifact preparation within the same credential-free container; no candidate evaluation before the failure",
+  "observation": "Exact-version metadata and tarball were available, but npm install received 404 for the package installation metadata; the same unchanged submission passed on retry. This is an endpoint-visibility observation, not a latency benchmark.",
+  "retainedDiagnostics": "https://github.com/volter-ai/twin-catalog-rollout-test/actions/runs/37350037621",
+  "confirmationPolicySource": "registry-confirmation.json",
+  "reproduce": "After a new immutable public test release, compare its exact-version endpoint with GET of the package endpoint using Accept: application/vnd.npm.install-v1+json; retain both responses and source/run identity. Do not republish an accepted version."
+}

package/docs/measurements/registry-confirmation.json

@@ -0,0 +1,13 @@
+{
+  "mode": "GitHub Actions npm publication and public registry GET",
+  "sourceCommit": "59469beb7c34fbadf6102fccc4a4f576907b309f",
+  "workflowRun": 37326269193,
+  "command": "node bin/twin-catalog.mjs publish --out dist; urllib.request.urlopen(exactVersionURL)",
+  "concurrentWork": "admission policy and durable-evidence verification in the same publisher job; no candidate tests or builds",
+  "postPublish404At": "2026-10-05T14:38:56.872636+00:00",
+  "confirmedAt": "2026-10-05T14:42:03.692478+00:00",
+  "observedConfirmationDelayUpperBoundSeconds": 186.819842,
+  "version": "0.2.7",
+  "integrity": "sha512-QbilRGDn7YtSeGPOMOdlWlmHTSpQqtpq7nU1h20Z6QDm+cx1zmIJSlQ3h/TVtO6G33I1SLOtyzU5N/v6Hcw39w==",
+  "remeasure": "On a fresh public sandbox main commit, run node bin/twin-catalog.mjs publish --out dist in publish.yml, then repeat urllib.request.urlopen('https://registry.npmjs.org/@volter%2ftwin-catalog-sandbox/<exact-new-version>') with datetime.datetime.now(datetime.timezone.utc) until HTTP 200. Retain the workflow source SHA, first post-upload 404 time and first observed 200 time."
+}