Document AutoPCB route-refinement boundary - #19
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e3ed496019
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## First implementation slice | ||
|
|
||
| Add an `autopcb-refinement` example problem once AutoPCB exposes typed route-fragment windows. Until then, this document is the integration contract for keeping the two projects aligned. |
There was a problem hiding this comment.
If this implementation step is followed, Solverang will gain an AutoPCB-specific problem coupled to typed PCB route fragments, contradicting the repository requirement that Solverang remain physics-neutral. Keep the example in AutoPCB's adapter repository, or replace it here with a domain-neutral bounded-refinement example.
AGENTS.md reference: AGENTS.md:L13-L13
Useful? React with 👍 / 👎.
|
|
||
| ## First implementation slice | ||
|
|
||
| Add an `autopcb-refinement` example problem once AutoPCB exposes typed route-fragment windows. Until then, this document is the integration contract for keeping the two projects aligned. |
There was a problem hiding this comment.
This PR establishes a new integration contract and concrete follow-up work, but STATUS.md remains dated August 16 and describes an unrelated milestone without this compatibility boundary or next step. Update the ledger so the required handoff state accompanies this documentation change.
AGENTS.md reference: AGENTS.md:L3-L3
Useful? React with 👍 / 👎.
1 participant
Summary
Adds an integration-boundary document defining Solverang's role in the AutoPCB autorouter reset.
Solverang should act as a continuous-refinement engine behind AutoPCB's transactional route kernel: length/skew tuning, local bend/via movement, pair symmetry, and smooth residual optimization. It should not own hard PCB semantics or final route acceptance.
Relation to AutoPCB PR
Companion to
akiselev/autopcb#2.Validation
Documentation-only PR.