Accelerator Distribution and Licensing

Updated 2026-06-19 based on Weekly Briefing — 19 June 2026 — the three licensing open items remain unresolved and were routed back from the weekly review; no change to decisions or current state.

Status: active Started: 2026-06-16 Last touched: 2026-06-19

Why this project exists

To set up how Redstrata stores, versions, licenses and distributes its AI/Data accelerators — beginning with the Business Glossary Build Kit and the Glossary Test Harness — so they can be licensed to clients as Accelerators / Templates [S-2026-06-16-accelerator-distribution-setup].

Current state

• Approach defined in a setup guide and a companion work-breakdown record on disk at _ClaudeWorkspace/07 Home Configuration/ [S-2026-06-16-accelerator-distribution-setup].
• Organising principle: separate “build & version (internal)” from “license & deliver (external)” — clients receive a sealed, sanitised, versioned package, never access to the canonical repository [S-2026-06-16-accelerator-distribution-setup].
• Platform decision: start on Bitbucket (already licensed; enterprise clients Atlassian-heavy; manual low-volume delivery), with GitHub documented as the later upgrade for self-serve / scaled distribution (its Releases, template repositories and storefront + licence-key integrations win at scale) [S-2026-06-16-accelerator-distribution-setup].
• Bitbucket gaps acknowledged: no native Releases (emulated via a git tag plus a .zip in the repo Downloads area) and no one-click “Use this template” (clients fork) — both workable manually at low volume [S-2026-06-16-accelerator-distribution-setup].
• Licensing: proprietary commercial EULA shipped in every package, not open source; platforms do not enforce terms — control is contractual plus access revocation [S-2026-06-16-accelerator-distribution-setup].
• IP boundary: a hard /_internal/ exclusion keeps answer keys, ground truth, QA reports and the Test Harness scoring logic out of client packages; the Test Harness may become a separate higher-tier “validation pack” [S-2026-06-16-accelerator-distribution-setup].
• Delivery model confirmed by Paul as manual enterprise first; both Bitbucket and the GitHub upgrade path are documented in one guide at his request [S-2026-06-16-accelerator-distribution-setup].

Decisions made

• 2026-06-16 — Separate internal build/version from external license/deliver; clients never get repository access, only sealed versioned packages. Why: protects IP and gives clients an auditable, immutable version [S-2026-06-16-accelerator-distribution-setup].
• 2026-06-16 — Start on Bitbucket; treat GitHub as a deliberate later upgrade. Why: existing Bitbucket licence, Atlassian-native clients, manual low-volume model; GitHub’s distribution primitives only pay off at self-serve scale [S-2026-06-16-accelerator-distribution-setup].
• 2026-06-16 — License as a proprietary commercial EULA, not open source. Why: an OSS licence would permit free redistribution of the IP [S-2026-06-16-accelerator-distribution-setup].
• 2026-06-16 — Enforce a /_internal/ boundary and keep the Test Harness in its own repo. Why: answer keys / ground truth / scoring logic must never ship in a client package [S-2026-06-16-accelerator-distribution-setup].

Open questions / blockers

• Commercial EULA drafting (legal review) and tier definitions — Evaluation / Commercial / Validation pack [S-2026-06-16-accelerator-distribution-setup].
• Whether the Glossary Test Harness ships as a separate licensed product or stays internal-only [S-2026-06-16-accelerator-distribution-setup].
• Pricing / contract model before first client delivery [S-2026-06-16-accelerator-distribution-setup].
• (2026-06-19, weekly review) All three items above remain unresolved as of the 19 June weekly briefing and were carried as the week’s top non-regulatory open loop; closing them is flagged as a suggested focus ahead of a first client delivery [S-2026-06-19-weekly-briefing].

Connected wiki pages

• derived-from → Paul Miles — Accelerator Distribution & Licensing Setup Guide — the setup guide and work-breakdown this project page summarises.
• relates-to → CLM Glossary Acceleration Squad — produces the Business Glossary Build Kit being licensed.
• relates-to → Taxonomy Knowledge Tool — the broader productisation context for client-deployable Redstrata tooling.
• relates-to → Practice Build — Phase 1 and Phase 2 Tools — this distribution capability supports Paul’s practice tooling. [inference]

History

• 2026-06-16 — Project created. Reviewed existing assets, researched GitHub / Bitbucket / digital-licensing options (June 2026), and confirmed Paul’s constraints (Bitbucket licence, Atlassian-heavy clients, manual enterprise delivery). Produced the setup guide (Bitbucket now + GitHub upgrade path) and a work-breakdown record; recorded the approach to Open Brain and this vault.

Sources / notes

• [S-2026-06-16-accelerator-distribution-setup] → Paul Miles — Accelerator Distribution & Licensing Setup Guide
• [S-2026-06-19-weekly-briefing] → Weekly Briefing — 19 June 2026 — weekly review confirming the three licensing items remain open.