Give the foundation a collection, a purpose, and a name.

They are not separate Toshokann modes. Both use the same extension and catalog contracts; their difference is what the steward promises about selection, revision, retention, and access.

1. Create an independent repository

   Fork or clone the complete Toshokann source, preserve it as an upstream when useful, and copy the empty reference extension under the derivative's own safe identifier.

2. Declare application, identity, and catalog

   Give the derivative its own canonical application ID for the inherited application-scoped DBOPFS path. Use defineExtension(config) to name it, point to its catalog, set empty-state language, and declare its bounded facets and navigation.

3. Keep provider authority explicit

   The neutral librarian is part of the inherited application, but Toshokann supplies no credential or product-trained model alias. Configuring a remote provider is an explicit user or derivative decision that may transmit collection text.

import { defineExtension } from '../../src/core/extension.js';

export default defineExtension({
  schemaVersion: 1,
  id: 'example-library',
  displayName: 'Example Library',
  description: 'Approved knowledge and resources for Example.',
  catalogUrl: './extensions/example-library/catalog.json',
  emptyState: {
    title: 'No records available',
    message: 'Add approved records to this catalog.'
  },
  facets: [
    { id: 'category', label: 'Category', field: 'category' },
    { id: 'record-type', label: 'Record type', field: 'kind' },
    { id: 'topic', label: 'Topic', field: 'tags' }
  ],
  navigation: [],
  library: {
    seedPrefix: 'example-library--',
    manifestVersionKey: '.example-library-manifest-version.json',
    refreshEvent: 'example-library-documents-refreshed',
    synonymGroups: []
  },
  assistant: {
    enabled: true,
    displayName: 'Example Librarian'
  }
});

Place approved Markdown below the selected extension. The compatible adapter normalizes established record aliases for title, path, summary, taxonomy, access, people, contacts, and source links, so an existing collection does not need a destructive schema rewrite.

{
  "schemaVersion": 1,
  "version": "2026-08-13",
  "documents": [
    {
      "id": "getting-started",
      "title": "Getting Started",
      "summary": "A concise guide to the approved workflow.",
      "path": "documents/getting-started.md",
      "name": "getting-started.md",
      "tags": ["onboarding"],
      "categories": ["operations"],
      "resourceTypes": ["guide"],
      "access": "public"
    }
  ]
}

Managed holdings

Packaged Markdown uses stable filenames below the active extension's DBOPFS seed prefix.

User holdings

Non-managed user Markdown remains visible and survives a managed catalog refresh.

Retrieval

Ranking and filters use normalized metadata; matched Markdown is bounded by per-document and total context character limits.

Release control

The compatible hydrator does not independently verify a catalog digest. Add and test a signed or hash-bound release layer when a derivative requires one.

Point the composition seam

Change src/active-extension.js to export the new extension. Shared core modules must never import derivative code.

Create a separate runtime package profile

Keep toshokann.package.json documentation-only. In a separate runtime descriptor, positively include all six application views, manifest, source, components, prompts, exactly one derivative extension, the complete vendored Arcane browser runtime, strong-type notices/runtime, license material, and approved holdings.

Own the public identity

Update product metadata, README art and copy, support language, package ID, manifest, Pages labels, and the derivative's own tests.

• Validate the selected extension

  Import it, load every packaged Markdown path, and prove that first-run inspection, managed refresh, user-upload preservation, search, preview, and librarian context work for its catalog.

• Test the derivative surfaces

  Replace Toshokann-specific site and README assertions. Test the derivative identity, internal links, empty and populated states, and product-specific policy.

• Inspect the exact artifact

  Run npm run check, serve dist locally, and verify that only the selected derivative and intended public records were packaged.

Toshokann can catalog, import, retrieve, and bound published Markdown snapshots. It does not by itself provide cryptographic release provenance, authenticity, chain of custody, timestamping, WORM storage, records schedules, legal hold, replication, migration, rights management, or preservation certification.

The current catalog hydrates UTF-8 text only. PDF, image, audio, and video support requires a new validated media contract and safe renderer. Browser-local imports are working copies, not accessions or preserved holdings.