History
Previous design nodes and their relation to current SCQ design targets.
History owns done, superseded, rejected, or archived design nodes. It keeps old design evidence available without mixing completed work into active Design Targets.
History Node Contract
Each history node should include:
| Field | Meaning |
|---|---|
| Status | Done, superseded, rejected, archived, or replaced. |
| Design summary | What was designed or evaluated. |
| Parameter snapshot | The same table shape used by current design targets. |
| Decision result | What the team learned or decided. |
| Related sources | Exact source identities and supported claims, linked through Knowledge References. |
| Relation to current work | Current or potential targets that cite this history node. |
| Artifacts | Links to approved summaries, not raw simulation or layout outputs. |
Relation Model
Use links for simple history. Use Mermaid only when the relation becomes easier to read as a tree or graph.
flowchart LR
HistoryNode["history node"]
CurrentTarget["current design target"]
ParameterTable["parameter table"]
PaperPage["Knowledge References"]
HistoryNode --> CurrentTarget
CurrentTarget --> ParameterTable
CurrentTarget --> PaperPageRaw simulation output, layout source, and solver artifacts stay in owner repos or approved artifact locations. History records the design decision trail.
Archived Reviews
Project-specific archived reviews remain with their classified source owners. No public archived review is listed in this publication.