coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The TargetRevenueLicense Framework is a canonical and extensible system for monetizing product exploration, software development, operation, services, consulting, sponsorship and other value-producing activities to drive open source and knowledge creation and evolution.
9 commits 1 branch 0 tags 2.4 MiB
Find a file
tegwick 4496244bb8 Adapt specs and workplans to SWOT Stage 0 sequencing 
Introduce SCOPE, expanded README, CONTRIBUTING, and provisional open-question
defaults. Rescope Trust Service work to offline schemas/fold/fixtures, add
normative core extraction workplan, and split PRD roadmap Phase 4 into
foundation vs hosted service. Sync workplans with State Hub.
2026-07-28 18:34:10 +02:00
history Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
spec Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
specs Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
workplans Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-28 18:33:47 +02:00
.repo-classification.yaml Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
CONTRIBUTING.md Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
INTENT.md Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
LICENSE Initial commit 2026-07-28 15:37:32 +00:00
README.md Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
SCOPE.md Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00
WORK-RECORDS.md Adapt specs and workplans to SWOT Stage 0 sequencing 2026-07-28 18:34:10 +02:00

README.md

target-revenue

Status: Concept and specification only (Stage 0). Not production legal text. Do not attach TRSL to production software yet.

The Target Revenue Framework (TRF) is a phased software monetization system: a defined development Phase accumulates Development Credit and Remission Credit against an immutable Initial Target until the Milestone Release automatically converts to a permissive Future License (MIT or Apache-2.0). A Trust Service publishes manifests, ledgers, extensions, and attestations as factual evidence — it does not decide conversion.

Commercial beneficiaries fund the creation and early availability of a software improvement; once the declared target is satisfied, the governed release becomes permissively open source.

Terminology guardrail

Before conversion, software under TRSL is source-available with commercial-use restrictions. It is not Open Source under the OSI Open Source Definition (field-of-endeavour non-discrimination). After the Conversion Event, the Milestone Release is available under the declared OSI-style Future License.

State Accurate label
Pre-conversion, noncommercial Source-available (permitted uses)
Pre-conversion, commercial Commercially licensed / entitlement required
Post-conversion Open source under Future License

Reading order

  1. INTENT.md — durable purpose and design principles
  2. SCOPE.md — what is in scope now vs later maturity
  3. spec/TargetRevenueLicenseConcept.md — normative concept (§1–10 for the kernel)
  4. specs/ProductRequirementsDocument.md — goals, FRs, roadmap
  5. specs/TechnicalSpecificationDocument.md — schema field tables and boundaries
  6. specs/OpenQuestions-WorkingDefaults.md — provisional Stage 0 defaults

Exploration transcript (non-normative): history/260728-InitialExploration.md
Program assessment: history/260728-SWOT-Assessment.md

Repository layout

Path Role
INTENT.md Stable purpose (change rarely)
SCOPE.md Living Stage 0 scope
spec/ Normative concept source (TargetRevenueLicenseConcept.md)
specs/ Product/tech specs, working defaults, future normative extracts
workplans/ Active delivery plans
history/ Dated non-normative exploration and assessments
examples/ Golden Phase packages (planned; WP-0002)
schemas/ Machine-readable schemas (planned; WP-0002)

spec/ vs specs/: The concept document predates the plural specs/ directory and remains under spec/ so history and cross-references stay stable. New product/tech artifacts go under specs/. Do not move the concept file without a deliberate migration note.

Active work

Workplan Focus
TREV-WP-0001 Prior-art research → non-binding TRSL draft skeleton
TREV-WP-0002 Schemas, pure Outstanding Target fold, golden fixture (not full service)
TREV-WP-0003 Extract stable normative core docs (PRD Phase 1)

Hub index: WORK-RECORDS.md · brief: .custodian-brief.md

What this repo does not claim yet

  • Final legal license text or enforceable TRSL
  • A running production Trust Service
  • A finalized degeneration formula (research + working defaults only)
  • That any real product Phase is governed by TRF today

See SCOPE.md and CONTRIBUTING.md.

License

Repository contents are under MIT No Attribution unless a file states otherwise. That is the license of this repository, not the Target Revenue Source License for third-party software.