Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/development/DEVELOPMENT_LOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,19 @@ reachable from any live state and `abandoned` from `parked`.

## Active

### DL-#59 · Deferred Validation Project Projection

- **State:** in_review
- **Owner:** codex
- **Issue:** #59; parents Repository_Management#1687 and Runner_Dashboard#1248
- **Branch:** `docs/deferred-project-projection`
- **PR:** https://github.com/D-sorganization/Launch-Monitor-Data/pull/60
- **Paths:** `docs/project/`, `docs/development/HANDOFF.md`
- **Started:** 2026-09-23
- **Last verified:** 2026-09-23 (265bcc7 plus docs; strict catalog and both parsers pass, two parked plans/six decisions; 49 tests and Ruff pass; unchanged local corpus.py:193 typing limitation retained)
- **Summary:** Exposes both published external dependencies and pending decisions without inventing evidence or authority. Existing client, rights and data-custody contracts are preserved.
- **Next step:** Protected publication, default-branch verification, then actual deployed Projects/staff adoption under the fleet parents.

### DL-#8 - Deferred Paired Data Dependency

- **State:** in_progress
Expand Down
23 changes: 23 additions & 0 deletions docs/development/HANDOFF.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,26 @@
# Deferred Validation Project Projection — #59

- Worktree: `C:/Users/diete/Repositories/Worktrees/Launch-Monitor-Data-deferred-project`.
Branch `docs/deferred-project-projection`; base `265bcc7`; commit `SELF`.
PR: [#60](https://github.com/D-sorganization/Launch-Monitor-Data/pull/60), open. Governing issue #59; parents Repository_Management#1687 and
Runner_Dashboard#1248. Development-log entry DL-#59.
- Added initial project charter/status views for DV-8 and DV-18, with owner links,
parked status and six pending Board/prerequisite decisions. Counts describe
this external-dependency slice only. Original plans and snapshots are unchanged.
- Public/client code, private-data lock, data rights and cohort eligibility are
unchanged. No private data, physical results, permissions or consent added;
this work does not authorize contacting rights holders.
- Validation: strict catalog valid; actual central/dashboard parsers agree on
two parked plans and six decisions. All 49 public client tests and Ruff
lint/format pass. Local mypy reproduces the previously documented unused-ignore
error in unchanged `src/launch_monitor_data/corpus.py:193` (16 files checked).
Hosted qualification remains required; no ignore or gate was weakened.
- Next: publish through protected CI, verify default-branch artifacts, then
inspect the deployed Projects API/UI. Staff deployment and the complete fleet
rollout remain open under their parent issues.

---

# Deferred External Work Split - 2026-09-22

- Repository/worktree: Launch-Monitor-Data,
Expand Down
32 changes: 32 additions & 0 deletions docs/project/CHARTER.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Launch Monitor Data Project Charter

## End Goal

Provide share-safe schemas, validation code and an authenticated client for the
private launch-monitor data authority. Preserve source identity, units, rights
and cohort eligibility. The [README](../../README.md) describes the wider
platform; this initial feature list covers only deferred external dependencies,
so its counts do not measure whole-repository progress.

## Non-Goals

- Publish private shot data, source artifacts or participant information.
- Infer licenses, consent, measurements or campaign approval from software tests.
- Manufacture paired shots from aggregate observations.
- Assign unavailable collection or rights-holder responses to coding agents.

## Features

| ID | Feature | Status | Tracking | Notes |
| --- | --- | --- | --- | --- |
| DV-8 | Qualified paired-device evidence from the owning campaign | parked | - | DV-8: [Owner Plan](https://github.com/D-sorganization/Launch-Monitor-Data/blob/main/docs/development/planning/DV-8.md); Board decision pending; authorized native exports and acquisition/rights evidence unavailable. |
| DV-18 | External redistribution and participant-consent decisions | parked | - | DV-18: [Owner Plan](https://github.com/D-sorganization/Launch-Monitor-Data/blob/main/docs/development/planning/DV-18.md); Board decision pending; authorized outreach ownership and actual permissions unavailable. |

## Source Authority

The [catalog](../development/planning/catalog.json), owner plans and original
source snapshots retain acceptance and reactivation requirements. Software,
existing-source research and available-data analysis remain separate executable
work under their original issues. This projection supplies no new evidence or
outreach authorization. The private campaign retains collection/data authority;
update the owner record before refreshing this projection.
39 changes: 39 additions & 0 deletions docs/project/STATUS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
<!-- generated by project-steward; do not hand-edit -->

# Launch Monitor Data Project Status

Initial planning projection generated by Codex on 2026-09-23 from the published
catalog at `265bcc7`. No scheduled Staff Hub execution, collected shots or
rights-holder approval is asserted. These two scopes are external dependencies,
not a whole-repository progress assessment.

## Progress

| ID | Feature | Status | Progress | Last Change |
| --- | --- | --- | --- | --- |
| DV-8 | Qualified paired-device evidence | parked | Awaiting verified prerequisites | 2026-09-23 |
| DV-18 | Redistribution and consent decisions | parked | Awaiting verified prerequisites | 2026-09-23 |

## Blockers

Native paired-device exports and their rights/calibration/acquisition identities
are unavailable for this next stage. External permissions and accountable
outreach ownership remain unverified. Existing public-client and cohort guards
continue to enforce their current contracts; no private lock or eligibility
policy changes are implied.

## Decisions Needed

- DV-8: Board decision pending on whether to resource the [Owner Plan](https://github.com/D-sorganization/Launch-Monitor-Data/blob/main/docs/development/planning/DV-8.md); accountable owner, funding, access dates and execution capacity remain unverified.
- DV-8: Decide how to obtain authorized native paired-device exports through the owning campaign; prerequisite evidence remains unavailable.
- DV-8: Decide how to qualify rights, calibration/firmware/environment identity and group-safe acquisition metadata; prerequisite evidence remains unavailable.
- DV-18: Board decision pending on whether to resource the [Owner Plan](https://github.com/D-sorganization/Launch-Monitor-Data/blob/main/docs/development/planning/DV-18.md); accountable owner, funding, access dates and execution capacity remain unverified.
- DV-18: Assign an authorized outreach owner and source-specific contact records before any outreach; ownership and authorization remain unverified.
- DV-18: Decide how to obtain explicit data licenses and participant-consent confirmation where needed; actual permissions remain unavailable.

## Reactivation

Follow the original plans: record Board decisions, accountable execution owners
and reviewed prerequisite evidence, then link bounded activation issues. Keep
private data and controlled permissions in their authorized stores. Reuse the
existing campaign rather than creating a competing experiment authority.
Loading