target-revenue/workplans/TREV-WP-0009-control-plane-and-effort-calculator.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated
TREV-WP-0009	workplan	Target Revenue Control Plane and Development Effort Calculator	infotech	target-revenue	active	claude	infotech	2026-07-30	2026-07-30

Target Revenue Control Plane and Development Effort Calculator

Builds the two pieces the maintainer identified as needed to move from "license text adopted org-wide" (history/260730-TRSL-OrgWideLicenseRollout.md) toward actually declaring real Phases with defensible Initial Targets:

1. A Control Plane — an interactive UI over the hosted Trust Service (workplans/TREV-WP-0006-trust-service-implementation.md, finished), usable by a human user with appropriate rights acting as the binky tenant, to interactively register Phases and — the specific, named requirement — create Development Credit ledger entries interactively rather than via raw API calls or the CLI.
2. A Development Effort Calculator — turns measurable repo activity (human interaction time, workplan/task volume, file/line complexity, AI token cost) into target_basis values (specs/PhaseManifestSpecification.md), which combined with a human Target Multiple classification (10x/100x/1000x) produces a proposed Initial Target via the framework's own existing formula (specs/TargetRevenueFrameworkCore.md §1.4) — not a new formula.

Does not include: declaring any real Phase for any repo. Both deliverables here are inputs to that decision (workplans/TREV-WP-0008-governance-and-pilot-rollout.md T05), not a way to bypass it.

Development Effort Calculator — formula decision (human gate)

id: TREV-WP-0009-T01
status: todo
priority: high
human_accept_required: true

specs/DevelopmentEffortCalculatorConcept.md §3 presents two combination strategies without choosing between them: Candidate A (labor-cost- anchored — human time drives estimated_effort_days/daily_rate, token cost becomes approved_direct_costs, workplan/file metrics are a sanity check) or Candidate B (composite-index-anchored — all four metric families scored into one complexity index, converted via a $-per-unit rate). Confirm one as the adopted v0 approach (or propose a refinement), per the same human-gate pattern already used for the degeneration policy formula (workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md T02). Agents may prepare a recommendation and leave this todo.

Control Plane user rights model — decision (human gate)

id: TREV-WP-0009-T02
status: todo
priority: high
human_accept_required: true

specs/TargetRevenueControlPlaneConcept.md §2 proposes a four-tier rights model (Viewer/Contributor/Operator/Admin) and recommends option (b) for the auth-attribution question (Control Plane holds the one Licensor token server-side, layers its own human-user auth/audit log in front of it, rather than requiring a WP-0006 schema change for per-human sub-credentials). Confirm the rights tiers and the (a)-vs-(b) choice, or propose a refinement. Agents may prepare a recommendation and leave this todo.

Implement Development Effort Calculator

id: TREV-WP-0009-T03
status: todo
priority: high

Using T01's confirmed formula, implement the calculator: data collection (commit-timestamp clustering for human time; workplan/task counts via state hub list_tasks/list_workplans or direct workplans/ directory inspection; file/line counts with generated/vendored-path exclusion per specs/DevelopmentEffortCalculatorConcept.md §2c's flagged distortion; token cost via get_token_summary(scope="repo", id=...)), and the combination formula itself, producing target_basis field values ready to drop into a Phase Manifest. Output must show its work (which inputs produced which numbers) — a black-box dollar figure with no visible derivation would undermine the "transparent, non-gameable" goal (specs/TargetRevenueLicenseConcept.md §4.6) this whole framework is built around.

Implement Control Plane (backend + interactive UI)

id: TREV-WP-0009-T04
status: todo
priority: high

Using T02's confirmed rights model, implement the Control Plane: human user authentication, the rights-tiered action set from specs/TargetRevenueControlPlaneConcept.md §3–§4 (interactive Development Credit entry creation as the priority flow), and the Control Plane's own audit log distinct from the Trust Service's signed records (§5). Reuses the existing hosted Trust Service API (service/app.py) as its backend without modification unless T02 specifically selects the per-human-sub-credential option, in which case that WP-0006 auth extension is this task's prerequisite, not an assumed given.

Apply calculator to real candidate repos

id: TREV-WP-0009-T05
status: todo
priority: medium

Once T03 is implemented, run it against the real candidates already identified (specs/PilotPhaseCandidateSurvey.md: net-kingdom's NK-WP-0002, railiance-apps's vergabe-teilnahme, and info-tech-canon's service surface) to produce proposed, calculator- derived target_basis values, replacing the hand-picked illustrative figures currently in examples/pilot-candidates/*/manifest.json. This remains draft/non-binding — updating a draft manifest's numbers is not a Phase declaration, and does not touch workplans/TREV-WP-0008-governance-and-pilot-rollout.md T05's own gate.