chore: clean hydrotech-beam syncthing conflicts and add new docs
- Remove all .sync-conflict-* files - Remove temp _temp_part_properties.json files - Add USER_GUIDE.md - Add dashboard docs (Executive, Technical, Operations, Master Plan) - Add playbooks (DOE, NX_REAL_RUN, SYNCTHING_RECOVERY) - Update iteration results Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
33
projects/hydrotech-beam/dashboard/EXECUTIVE_DASHBOARD.md
Normal file
33
projects/hydrotech-beam/dashboard/EXECUTIVE_DASHBOARD.md
Normal file
@@ -0,0 +1,33 @@
|
||||
# Hydrotech Beam — Executive Dashboard
|
||||
|
||||
Last updated (UTC): 2026-02-14T22:24:29
|
||||
Source: `studies/01_doe_landscape/results/doe_summary.json` + `doe_results.csv`
|
||||
|
||||
## CEO 60-second view
|
||||
- **Phase:** DOE Phase 1 (LHS)
|
||||
- **Gate status:** ❌ **BLOCKED** (Phase 1 → Phase 2)
|
||||
- **Total trials:** 51
|
||||
- **Solved:** 39 (**76.5%**, below 80% gate)
|
||||
- **Geo-infeasible:** 12
|
||||
- **Fully feasible designs:** 0 (gate requires ≥5)
|
||||
|
||||
## Top signals
|
||||
- ✅ Mass extraction now looks real (no NaN in solved rows)
|
||||
- ✅ Syncthing cleanup completed (active conflict files archived)
|
||||
- ⚠️ Displacement constraint is the blocker (0/39 displacement-feasible at 10 mm)
|
||||
- ⚠️ DOE→TPE gate cannot pass with current limits/bounds
|
||||
|
||||
## Decision hotlist (CEO)
|
||||
1. **Approve next constraint strategy**:
|
||||
- Option A (recommended): exploratory rerun at **20 mm** displacement
|
||||
- Option B: keep 10 mm and tighten design bounds for stiffness
|
||||
2. **Approve TPE entry rule** (with strict gate or conditional gate)
|
||||
|
||||
## Recommendation (current)
|
||||
Proceed with **Option A** for exploration (20 mm), then tighten toward 10 mm in staged optimization.
|
||||
|
||||
## KPI snapshot
|
||||
- Solve success rate: **76.5%**
|
||||
- Feasibility rate (full): **0.0%**
|
||||
- Best solved mass: **686.289 kg** (not fully feasible)
|
||||
- Best trial ID by mass: **26**
|
||||
194
projects/hydrotech-beam/dashboard/MASTER_PLAN.md
Normal file
194
projects/hydrotech-beam/dashboard/MASTER_PLAN.md
Normal file
@@ -0,0 +1,194 @@
|
||||
# Hydrotech Beam — Dashboard & Reporting Master Plan (Multi-LLM Synthesis)
|
||||
|
||||
## Purpose
|
||||
Give Antoine a single, reliable command view of project health while preserving full technical depth and operational traceability.
|
||||
|
||||
This plan synthesizes recommendations from:
|
||||
- Codex 5.3 (execution architecture + contracts + KPI gates)
|
||||
- Opus 4.6 (PKM-first, markdown-native, low-overhead governance)
|
||||
- Gemini Pro (clear role-based dashboards + event-stream discipline)
|
||||
|
||||
---
|
||||
|
||||
## North-Star Architecture (Hybrid, future-proof)
|
||||
|
||||
### Phase 1 default (now): **PKM-native dashboards in markdown**
|
||||
- No new infrastructure required
|
||||
- Fastest path to value
|
||||
- Agent-native read/write and auditability
|
||||
|
||||
### Phase 2+ extension: **optional web UI over same contracts**
|
||||
- If/when needed for richer visual analytics
|
||||
- No rewrite: UI reads the same structured contracts and event logs
|
||||
|
||||
**Key principle:** Data contracts first, presentation second.
|
||||
|
||||
---
|
||||
|
||||
## 1) Information Architecture
|
||||
|
||||
## A. Project-specific (lives under `projects/hydrotech-beam/`)
|
||||
- `dashboard/` — generated dashboard markdown snapshots
|
||||
- `reports/` — run/phase/executive reports
|
||||
- `runs/` — run manifests and execution metadata
|
||||
- `decisions/` — append-only decision records
|
||||
- `incidents/` — sync/solver/process incident records
|
||||
- `playbooks/` — project execution procedures
|
||||
|
||||
## B. Foundational (lives under `docs/`)
|
||||
- `docs/guides/` — reusable dashboard/report standards
|
||||
- `docs/reference/data-contracts/` — versioned schema definitions
|
||||
- `docs/protocols/` — gates, QA, governance rules
|
||||
- `docs/templates/` — report and dashboard templates
|
||||
|
||||
---
|
||||
|
||||
## 2) Dashboard Modules (3-tier)
|
||||
|
||||
## A. Executive Dashboard (60-second scan)
|
||||
- Project status (RAG + phase + blockers)
|
||||
- Milestone confidence and slip risk
|
||||
- Decision hotlist (items needing CEO approval)
|
||||
- Top risks + mitigation owners
|
||||
- Gate state (Pass / Conditional / Fail)
|
||||
|
||||
## B. Technical Dashboard
|
||||
- DOE/TPE performance (success, feasible points, convergence)
|
||||
- Constraint panel (disp/stress/geo violations)
|
||||
- Data quality checks (NaN, stub-vs-nxopen, stale/mixed runs)
|
||||
- Traceability (requirement → run → result → decision)
|
||||
|
||||
## C. Operations Dashboard
|
||||
- Queue and throughput (WIP, cycle time, backlog)
|
||||
- Blocker tracker + MTTR
|
||||
- Review SLA status
|
||||
- Syncthing/data integrity panel
|
||||
- Documentation freshness/compliance
|
||||
|
||||
---
|
||||
|
||||
## 3) Data Contracts (mandatory)
|
||||
|
||||
All dashboard/report content must come from structured records with lineage.
|
||||
|
||||
Required contracts (v1):
|
||||
1. `run_manifest.v1.json`
|
||||
2. `trial_result.v1.json`
|
||||
3. `study_summary.v1.json`
|
||||
4. `decision_record.v1.json`
|
||||
5. `risk_record.v1.json`
|
||||
6. `gate_evaluation.v1.json`
|
||||
7. `incident_record.v1.json`
|
||||
|
||||
Required fields in every record:
|
||||
- `schema_version`, `project_id`, `run_id` (if applicable)
|
||||
- `timestamp_utc`, `owner`, `source_file`, `source_hash`
|
||||
|
||||
Ingestion rules:
|
||||
- Reject invalid schema
|
||||
- Keep append-only history for decisions/gates/incidents
|
||||
- Nightly integrity check + drift report
|
||||
|
||||
---
|
||||
|
||||
## 4) Report System
|
||||
|
||||
## A. Daily Ops Brief (auto)
|
||||
- Blockers, failures, overdue reviews, data integrity warnings
|
||||
|
||||
## B. Weekly Executive Brief (auto + curated)
|
||||
- Milestone confidence, top risks, decision asks, KPI trend deltas
|
||||
|
||||
## C. Gate Review Pack (formal)
|
||||
- Criteria checklist, evidence index, exceptions, sign-offs
|
||||
|
||||
## D. Technical Deep Dive (on-demand)
|
||||
- Methods, assumptions, sensitivity, reproducibility evidence
|
||||
|
||||
Render path:
|
||||
- Markdown source of truth
|
||||
- Optional HTML/PDF exports from templates
|
||||
- Immutable snapshot ID per issued report
|
||||
|
||||
---
|
||||
|
||||
## 5) Governance & Ownership
|
||||
|
||||
- **Manager (owner):** documentation architecture, dashboard governance, release quality
|
||||
- **Tech Lead:** technical KPI definitions, thresholds, validation logic
|
||||
- **Study Builder:** data pipeline and generators
|
||||
- **Optimizer:** analytics logic and recommendation layer
|
||||
- **Auditor:** contract compliance + gate QA
|
||||
|
||||
Rule enforced:
|
||||
- Project-specific content in `projects/...`
|
||||
- Foundational content in `docs/...`
|
||||
|
||||
---
|
||||
|
||||
## 6) KPI Set + Gate Rules (starter)
|
||||
|
||||
## KPI starter set
|
||||
- Solve success rate
|
||||
- Full feasibility rate
|
||||
- Best feasible mass
|
||||
- Constraint violation percentiles (disp/stress)
|
||||
- Data integrity score
|
||||
- Decision cycle time
|
||||
- Blocker MTTR
|
||||
- Documentation freshness lag
|
||||
|
||||
## Gate policy
|
||||
- Gate states: `PASS` | `CONDITIONAL_PASS` | `FAIL`
|
||||
- Conditional pass requires named owner + due date + risk acceptance
|
||||
- Hard fail blocks progression
|
||||
|
||||
DOE→TPE gate (initial):
|
||||
- Solve success ≥ 80%
|
||||
- Feasible points ≥ 5
|
||||
- Data integrity score ≥ 95%
|
||||
|
||||
---
|
||||
|
||||
## 7) Rollout Plan
|
||||
|
||||
## Phase 0 (48h)
|
||||
- Contract definitions + KPI dictionary
|
||||
- Dashboard markdown templates
|
||||
- Run manifest/logger enabled
|
||||
|
||||
## Phase 1 (1 week)
|
||||
- Live executive + operations dashboards
|
||||
- Daily ops brief + weekly executive brief
|
||||
|
||||
## Phase 2 (2–3 weeks)
|
||||
- Technical dashboard depth (DOE/TPE analytics, traceability)
|
||||
- Gate review packs with evidence linking
|
||||
|
||||
## Phase 3 (ongoing)
|
||||
- Optional web UI layer
|
||||
- Predictive risk signals and anomaly detection
|
||||
|
||||
---
|
||||
|
||||
## 8) Risks & Mitigations
|
||||
|
||||
1. Backend confusion (stub vs nxopen)
|
||||
- Mitigation: manifest hard-check + dashboard alert
|
||||
|
||||
2. Syncthing conflicts / stale truth
|
||||
- Mitigation: conflict detector + incident workflow
|
||||
|
||||
3. Schema drift
|
||||
- Mitigation: versioned contracts + validator + auditor checks
|
||||
|
||||
4. Dashboard sprawl
|
||||
- Mitigation: role-based views + KPI change control
|
||||
|
||||
5. Documentation decay
|
||||
- Mitigation: freshness SLA + automated stale flags
|
||||
|
||||
---
|
||||
|
||||
## Decision
|
||||
Proceed with **PKM-native dashboard/report system now**, built on strict contracts and governance, with a clean upgrade path to richer UI later.
|
||||
43
projects/hydrotech-beam/dashboard/OPERATIONS_DASHBOARD.md
Normal file
43
projects/hydrotech-beam/dashboard/OPERATIONS_DASHBOARD.md
Normal file
@@ -0,0 +1,43 @@
|
||||
# Hydrotech Beam — Operations Dashboard
|
||||
|
||||
Last updated (UTC): 2026-02-14T22:24:29
|
||||
|
||||
## Pipeline status
|
||||
- Study folder sync: ✅ healthy (latest artifacts visible)
|
||||
- Conflict artifacts: ✅ archived under `results/archive_conflicts_*`
|
||||
- Clean rerun archive: ✅ `results/archive_before_clean_rerun_*`
|
||||
|
||||
## Artifact integrity
|
||||
Active result files present:
|
||||
- `doe_results.csv`
|
||||
- `doe_summary.json`
|
||||
- `doe_run.log`
|
||||
- `history.csv`
|
||||
- `history.db`
|
||||
- `optuna_study.db`
|
||||
|
||||
## Process compliance
|
||||
- Backend clarity rule: must always run with explicit `--backend`
|
||||
- Documentation boundary rule: enforced
|
||||
- Project-specific docs → `projects/...`
|
||||
- Foundational standards → `docs/...`
|
||||
- New standards created:
|
||||
- `projects/hydrotech-beam/dashboard/MASTER_PLAN.md`
|
||||
- `docs/guides/PKM_DASHBOARD_STANDARD.md`
|
||||
- `docs/guides/DOCUMENTATION_BOUNDARIES.md`
|
||||
|
||||
## Current blockers
|
||||
1. Phase gate blocked (insufficient feasible designs)
|
||||
2. Need CEO decision on constraint path for next DOE/TPE sequence
|
||||
|
||||
## Next operational actions (owner)
|
||||
1. **Manager:** keep dashboards refreshed after every run
|
||||
2. **Tech Lead:** finalize recommended constraint staging
|
||||
3. **Study Builder:** prep reproducible command set for next run
|
||||
4. **Optimizer:** define TPE launch criteria + seed strategy
|
||||
5. **Auditor:** enforce gate criteria and data-contract checks
|
||||
|
||||
## SLA targets (initial)
|
||||
- Dashboard freshness: ≤ 1h after major run
|
||||
- Run log compliance: ≥ 95%
|
||||
- Decision backlog age: ≤ 48h
|
||||
43
projects/hydrotech-beam/dashboard/TECHNICAL_DASHBOARD.md
Normal file
43
projects/hydrotech-beam/dashboard/TECHNICAL_DASHBOARD.md
Normal file
@@ -0,0 +1,43 @@
|
||||
# Hydrotech Beam — Technical Dashboard
|
||||
|
||||
Last updated (UTC): 2026-02-14T22:24:29
|
||||
Source: `studies/01_doe_landscape/results/doe_results.csv`
|
||||
|
||||
## Study health
|
||||
- Trials: 51
|
||||
- Solved: 39
|
||||
- Geo-infeasible: 12
|
||||
- Solve failures: 0
|
||||
- Full-feasible: 0
|
||||
|
||||
## Constraint status
|
||||
- Displacement limit: **10.0 mm**
|
||||
- Stress limit: **130.0 MPa**
|
||||
|
||||
Observed solved ranges:
|
||||
- Tip displacement: **11.7788 → 39.4912 mm**
|
||||
- Max von Mises stress: **75.0116 → 398.4295 MPa**
|
||||
|
||||
Feasibility counts:
|
||||
- Displacement feasible: **0**
|
||||
- Stress feasible: **23**
|
||||
- Fully feasible: **0**
|
||||
|
||||
## Performance / runtime
|
||||
- Solve time range (solved): **12.42 s → 59.59 s**
|
||||
- Pattern indicates real NX execution (non-stub timing)
|
||||
|
||||
## Data quality checks
|
||||
- Mass NaN (solved): **0** ✅
|
||||
- Penalty mass (99999): **12** (geo infeasible trials) ✅ expected
|
||||
- Mixed appended run state: **cleared** (current clean 51-trial set)
|
||||
|
||||
## Technical interpretation
|
||||
- Current geometry space + 10 mm displacement limit appears too restrictive.
|
||||
- Stress limit is partially satisfiable (23/39), so the primary bottleneck is stiffness/displacement.
|
||||
|
||||
## Recommended technical next actions
|
||||
1. Run a controlled DOE with displacement limit = 20 mm (exploration mode)
|
||||
2. Identify near-feasible stiff regions
|
||||
3. Launch TPE with penalty + staged tightening toward 10 mm
|
||||
4. Re-run gate check with updated feasible counts
|
||||
Reference in New Issue
Block a user