Nishi Family › Compare › Brake Caliper Press Tool

Nishi Compare · capabilities, evidence and delivery

Brake Caliper Press Tool

Compare capabilities and delivery evidence. Source discovery, qualification, deployment and accepted outcomes are separate; an open contract names work still to verify.

Nishi even-pressure dual-piston caliper press with force indication (designed from the first bit up) vs single-plate spreaders and ratcheting dual-plate presses and rear wind-back kits and the EPB scan lane -- Aug-2026 field

Overview

The purpose, declared position and evidence coverage of this domain. Source presence and completed acceptance are different measures.

Where we are. MEASURED 2026-08-19: no Nishi hardware. In tree and measured: the product decomposer, the sovereign slicer, the landed-cost corridor engine and the sourcing-mix pricer. The field is mirrored: commodity single-plate spreaders, ratcheting dual-plate presses with no force feedback, rear wind-back kits, and the EPB scan lane that owns service mode on electronic parking brakes.

Where we need to go. OPERATOR ASK (2026-08-19): a better double brake caliper expander. The design thesis: even pressure BY GEOMETRY plus clamp-force indication with overload refusal plus a rear wind-back head plus an EPB workflow card -- the four capabilities the incumbent classes each hold one of and none holds together.

The unit. 1 u = one measured session-leg (organ plus gate plus live flip), the standing calibration.
Cost to a proven design pack: 3 u. BT1 force model against a load-cell fixture, BT2 even-press geometry with displacement-delta gate, BT3 fluid and EPB data cards.
Cost to a priced BOM and manufacturing verdict: 2 u more. BT4 composes lc_calc and sp_mix over the steel and hardware list. 5 u cumulative.
Cost to a bench-proven first article: 3 u more plus hardware. BT5 printed-fixture lane then machined prototype, BT6 bench gate on real dual-piston calipers. 8 u cumulative.

Research bar. The dual-plate ratcheting class, best incumbent is measured on the 2026 review field on multi-piston caliper presses. Theirs: dual push boards compress paired pistons evenly enough to win reviews [presspicks]. Ours: our BT2 gate must beat it MEASURABLY: piston displacement delta under a declared threshold on a dual-piston fixture, plus the force indication the class lacks [pistonpicks].

Business case

AxisPositionFiguresDecision
InvestmentDesign and gate legs are organ work; hardware exposure is one load-cell, printed fixtures and one machined prototype batchestimated 8 u to a bench-proven article; incumbent tools for teardown cost tens of dollars each [pistonpicks]fund the organ leg now; buy the three incumbent classes for teardown -- the cheapest competitive research in the estate
MarketThe caliper-tool shelf is a crowded commodity lane at the bottom [gjthread] and undifferentiated in the middle [presspicks]; nobody sells force-indicated even-pressthe wedge is the measured tool: even-press proof plus force gauge plus EPB card, priced above the ratchet class and below shop hydraulicssell the measurement, not the steel -- the gate results ship WITH the tool as its spec sheet
Opportunity costSmallest of the three product lanes; BT1 (thread mechanics) and BT4 (BOM costing) are reusable across the physical programlow blast radius, fast proof of the physical-lane workflowuse this lane as the pathfinder article for the physical-products program
Go to marketMechanics buy on forum reputation and review-field placement [gjthread] [presspicks]review-field placement is earned by the measured spec sheet no rival publishesseed the measured evenness and force data publicly; the honest spec IS the marketing
Buy vs buildEvery incumbent class is a cheap BUY today; the four-capability combination does not exist to buyBUILD only the combined article; BUY all three incumbent classes as teardown references [pistonpicks]build the wedge, buy the references

Latest recorded release

No valid dated release entry is recorded for this domain.

Release entries describe recorded changes; they do not establish that every capability passed evaluation.

7 of 14 capability source symbols found|2 of them authored stronger-claims|7 open|coverage 500/1000|adoption 3 full / 4 partial

Evidence profile — what the gaps on this board actually are

Measured by nx_swcompare_evidence, read back by nx_evprofile_lib. Every figure is a count with its denominator — there is deliberately no score, no grade and no percentage anywhere in this band, because a stored scalar is a field a seat can edit and a counted partition is not.

evidence|grounded 7/7|unsupported 0|gates green 0/0|proven able to fail n/a — no gate ran|green at 0/0 0|open gaps 7|of them unnamed 0|of them proof withheld 0|flips ready 0

proven able to fail counts the gates that have a RECORDED RED — nx_gate_bite mutated the gate subject, rebuilt it, watched the gate go red, and that record is inside the shared TTL. never bitten is its complement over the same denominator: those gates ran and were green, and nothing has ever shown them able to detect anything, so their green is a statement about this run and not about the gate. green at 0/0 is a separate and much weaker observation — the gate printed GREEN on a zero denominator, so its own tooth counter says it examined nothing. A gate can be green, non-zero, and still never bitten; that is the common case and it is now visible instead of implied.

partition: grounded + unsupported = 7 vs present 7 · named + unnamed + withheld = 7 vs open 7 · both reconcile

liar-kill conj=GPqN · first failing conjunct: quorum

graded document: BUILDROOT tree, 6087 bytes · gates map: NONE · stamped 36d 23h ago · STALE against the shared TTL of 604800s — this is evidence about a build nobody can vouch for now · source ../knowledge/status/evstamp_braketool.verdict

Gap classWhat it is, and the work it names
CLAIM-ONLYNo declared gate ran for this board, so every capability mark here rests on a symbol existing in source and on nothing executing. The remedy is to WRITE a .gates map naming gates that already run — authoring, not research.
STALEThis profile is older than the shared TTL, or its clock ran backwards. It is reported as unusable rather than as fresh, because being wrong in the direction of refusing is the safe direction.
This band reports the referee counts. The per-axis worklist rows — which axis is unsupported, which watch is ready to flip, which gap is unnamed — are printed by nx_swcompare_evidence braketool itself and are not carried on the stamp, so this page names the classes and the producer names the rows. That split is stated rather than hidden: a count without a worklist is not actionable, and this band is honest about which half of that it is.

Production map

Follow the dependencies, declared acceptance criteria and recorded priorities. Inspect source binding before treating a rank as executable work.

Ranking source binding: PLAN_MATRIX_BOUND_ONLY. Recorded priorities require current acceptance evidence and resource checks before execution.

Ranking matches the captured plan and matrix only. Latest execution outcome, research freshness, accepted delivery and investment return are unverified.

Recorded priority estimates

Order from nx_compare_rank (nx_dr_ocm: (deficit + cost-of-delay + option + enables) x sponsor x self-sufficiency x momentum / cost). FINISH rows are rungs whose symbol is present but whose organ is short of full adoption: listed before new work by this heuristic. Priority is not measured delivery cost or execution readiness. Stamp: # asof=1790081915 domain=braketool target_version=0.1 rungs=6 done=0 open=6 finish=0 ranker=nx_dr_ocm

#StageRungPriorityDerivation
#10.1Thread mechanics and clamp-force model (BT1) bt_force_model dossier3000v=30 m=1 c=10
#20.1Even-press geometry pack (BT2) bt_even_press dossier2000v=20 m=1 c=10
#30.1EPB and fluid data cards (BT3) bt_epb_flow dossier200v=2 m=1 c=10
#4laterBOM, landed cost and manufacturing verdict (BT4) bt_bom_cost dossier2000v=40 m=1 c=20
#5laterPrototype pack, printed then machined (BT5) bt_proto_pack dossier1000v=15 m=1 c=15
#6laterBench gate on real calipers (BT6) bt_bench_gate dossier0v=0 m=1 c=15

Declared roadmap — contract, acceptance, executor, effort

RungCloses withDefinition of done (pre-declared)ExecutorEst.
Thread mechanics and clamp-force model (BT1)bt_force_modelscrew pitch, friction and plate stiffness to force at handle, proven against a load-cell fixture gate; neg-control = a spec the model must refuseOrgan1 u
Even-press geometry pack (BT2)
after BT1
bt_even_pressdisplacement-delta gate on a dual-piston fixture; the trivial wrong implementation (single-point push) MUST fail the delta toothOrgan1 u
EPB and fluid data cards (BT3)bt_epb_flowmodel-family rows as DATA naming when a scan lane is required [foxwellepb] [epbreset]; fluid-volume model with the open-bleeder decision rowOrgan1 u
BOM, landed cost and manufacturing verdict (BT4)
after BT1
bt_bom_coststeel and hardware priced through lc_calc corridors and sp_mix domestic path; buy-vs-build table regenerates from itOrgan2 u
Prototype pack, printed then machined (BT5)
after BT2,BT4
bt_proto_packprinted plates and fixtures off the slicer for fit; machined article speced from BT1-BT2 outputsOrgan1.5 u
Bench gate on real calipers (BT6)
after BT5
bt_bench_gatemeasured compressions on declared single, dual and rear-EPB fixtures; force ceiling refusal witnessed; REFUSES on partial fixture coverageOrgan1.5 u

Milestones

MilestoneRungsCumulative
M0 · Design pack provenBT1,BT2,BT33 u
M1 · Priced and sourcedBT45 u
M2 · Bench-proven articleBT5,BT68 u
Ladder verdict. NOT DECLARED. This board names no dated best-in-class or frontier target and no rung roles (sotatarget and rungrole rows on its plan); the ranker labels it NO-LADDER until it does, and until then its rungs climb toward a target nobody has written down. Bars read NO-BAR against the current month 2026-10.
Bar freshness, counted
ClassCountNote
bars0sotabar rows on the plan
fresh0the bar month is the current month
attested0an older bar with a this-month barscan reporting no newer entry
stale0a this-month scan saw a newer month the bar ignores
unattested0nobody looked this month
malformed0a sotabar row missing a field
duplicate0bar ids an earlier row already carries
bars, summed0RECONCILED: the parts sum to the total 0
current month2026-10the month every bar is judged against
Treatment verdict. NOT DECLARED. No rung on this board declares its three-step treatment (a treat row naming the MCP row, the API route, the primitive it composes, the workflow that composes it and the agent beat that runs it); the ranker labels every rung TREATMENT-UNDECLARED until it does.

Inspect a rung and its prerequisites

Declared nodes 6. Rank input binding: PLAN_MATRIX_BOUND_ONLY. Dependency order is authored. Implementation, acceptance evidence, authority and resource readiness are unverified. No action is recommended or dispatched here.

Plan SHA-256 ec9c5240e7c6a1b7ac67578f55b02e095b4ba2c6ebe6a2ba02fc1adca9e8ff54. Target rows 0; role rows 0. Existing risks and release worklog retain their own scope; no node completion is inferred.

Runtime observation coverage: 0 of 6 rungs have current, identity-bound execution observations. Observation may report RED. Accepted completion remains unknown; source presence, qualification and deployment do not establish it.

Use Enter or Space on a rung to inspect its contract. Prerequisite links locate another rung in this list; open its summary to inspect it. Estimates are authored effort, not forecasts.

  1. BT1 — Thread mechanics and clamp-force model

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: bt_force_model

    Acceptance: screw pitch, friction and plate stiffness to force at handle, proven against a load-cell fixture gate; neg-control = a spec the model must refuse

    Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

  2. BT2 — Even-press geometry pack

    Prerequisites: BT1 (acceptance unverified)

    Contract: bt_even_press

    Acceptance: displacement-delta gate on a dual-piston fixture; the trivial wrong implementation (single-point push) MUST fail the delta tooth

    Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

  3. BT3 — EPB and fluid data cards

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: bt_epb_flow

    Acceptance: model-family rows as DATA naming when a scan lane is required [@foxwellepb] [@epbreset]; fluid-volume model with the open-bleeder decision row

    Authored effort: 1. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

  4. BT4 — BOM, landed cost and manufacturing verdict

    Prerequisites: BT1 (acceptance unverified)

    Contract: bt_bom_cost

    Acceptance: steel and hardware priced through lc_calc corridors and sp_mix domestic path; buy-vs-build table regenerates from it

    Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

  5. BT5 — Prototype pack, printed then machined

    Prerequisites: BT2 (acceptance unverified), BT4 (acceptance unverified)

    Contract: bt_proto_pack

    Acceptance: printed plates and fixtures off the slicer for fit; machined article speced from BT1-BT2 outputs

    Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

  6. BT6 — Bench gate on real calipers

    Prerequisites: BT5 (acceptance unverified)

    Contract: bt_bench_gate

    Acceptance: measured compressions on declared single, dual and rear-EPB fixtures; force ceiling refusal witnessed; REFUSES on partial fixture coverage

    Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

Learning and practice paths

No structured learning path is declared for this plan. Existing research, roadmap and worklog remain available above.

Rung dossiers — every record that bears on a rung, in one place

Joined by symbol, never typed. Each dossier is assembled on every publish from the rows this board already carries: the plan's rung row, the matrix row that carries its contract symbol (its status re-measured by the one symbol ruler), the gate the organ declares and the verdict the evidence referee recorded on its last run, the reference marks in the rung text, the design rows that name the rung and the work log filed against it. The capability matrix links each cell to its dossier and each dossier links back to its cell and forward to the rungs it stands on; a dependency naming no rung on this plan is written as UNRESOLVED rather than linked. Absences are named: NO-MATRIX-ROW, NO-GATE-DECLARED, UNRECORDED.
Gate verdicts: UNSTAMPED — no per-gate verdict artifact is published for this domain yet (nx_swcompare_evidence braketool writes it beside its stamp); every gate below reads UNRECORDED until it runs.
Gate declarations: knowledge/organ_gate.conf read from this working directory (1 rows) and from the estate root (196 rows); rows in both counted once: 0; declarations read: 197. Every declaration in either copy counts, so a stub beside the publisher can never hide the root.
BT1 Thread mechanics and clamp-force model · cell WATCHING · gate NO-GATE-DECLARED
Contractbt_force_model · executor Organ · 1 u · stands on nothing
Definition of donescrew pitch, friction and plate stiffness to force at handle, proven against a load-cell fixture gate; neg-control = a spec the model must refuse
Matrix cellDESIGN: Thread mechanics and clamp-force model · runtime/nx_braketool.nx · WATCHING decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_braketool; declare nx_braketool TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
BT2 Even-press geometry pack · cell WATCHING · gate NO-GATE-DECLARED
Contractbt_even_press · executor Organ · 1 u · stands on BT1
Definition of donedisplacement-delta gate on a dual-piston fixture; the trivial wrong implementation (single-point push) MUST fail the delta tooth
Matrix cellPRESS: Compress dual and quad pistons EVENLY, no piston cocking · runtime/nx_braketool.nx · WATCHING decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_braketool; declare nx_braketool TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
BT3 EPB and fluid data cards · cell WATCHING · gate NO-GATE-DECLARED
Contractbt_epb_flow · executor Organ · 1 u · stands on nothing
Definition of donemodel-family rows as DATA naming when a scan lane is required [foxwellepb] [epbreset]; fluid-volume model with the open-bleeder decision row
Matrix cellSAFETY: EPB service-mode workflow, motor retract before press · runtime/nx_braketool.nx · WATCHING decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_braketool; declare nx_braketool TAB <gate> and the ship loop proves it and the verdict lands here.
Work logno log row names this rung yet
BT4 BOM, landed cost and manufacturing verdict · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW
Contractbt_bom_cost · executor Organ · 2 u · stands on BT1
Definition of donesteel and hardware priced through lc_calc corridors and sp_mix domestic path; buy-vs-build table regenerates from it
Matrix cellNO-MATRIX-ROW — no matrix row carries bt_bom_cost; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gatethe gate join needs a matrix row: no organ is named for this rung
Work logno log row names this rung yet
BT5 Prototype pack, printed then machined · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW
Contractbt_proto_pack · executor Organ · 1.5 u · stands on BT2, BT4
Definition of doneprinted plates and fixtures off the slicer for fit; machined article speced from BT1-BT2 outputs
Matrix cellNO-MATRIX-ROW — no matrix row carries bt_proto_pack; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gatethe gate join needs a matrix row: no organ is named for this rung
Work logno log row names this rung yet
BT6 Bench gate on real calipers · cell NO-MATRIX-ROW · gate NO-MATRIX-ROW
Contractbt_bench_gate · executor Organ · 1.5 u · stands on BT5
Definition of donemeasured compressions on declared single, dual and rear-EPB fixtures; force ceiling refusal witnessed; REFUSES on partial fixture coverage
Matrix cellNO-MATRIX-ROW — no matrix row carries bt_bench_gate; the ranker reads this rung as unmapped and no cell can flip for it. Add the row and the join completes on the next publish.
Gatethe gate join needs a matrix row: no organ is named for this rung
Work logno log row names this rung yet

dossiers=6 cells_joined=3 no_matrix_row=3 (sum 6) gates_recorded=0 gates_unrecorded=0 no_gate_declared=3 (sum 3 of cells_joined) evgates=UNSTAMPED

Capability comparisons

Compare the field, search individual capabilities and open their source and adoption evidence. Documented presence does not establish comparative quality.

Position map — centrality and distinctiveness

The four-quadrant map the field uses for brand strategy (Dawar and Bagga, HBR June 2015), re-derived from this matrix on every publish. Centrality is the share of the category's feature mass a player covers, each feature weighted by how many hold it; distinctiveness is the average lead over each rival on the rows the player holds; breadth is the depth-weighted share of the whole matrix (the bubble); depth is how deeply the rows held are held; momentum is the day-over-day move off the spine (green rising, red falling, grey until day two); the dashed path runs first day → previous day → today. Dividers are the category means. Axes are fitted to the field of play, so read the tick numerals, not the frame. Rival marks are documented presence, so a rival's position reads the record, never its quality. The picture grades its own readability below; the table beside it is the same data for a screen reader or a second method.

Rows. 14 feature rows mapped of 14 matrix rows; 0 substrate rows (kernels, bounds and instruments the plan's rungrole marks substrate) are the estate's scaffolding, not category features, and stay off the map
Views. 2D cut: centrality, distinctiveness · 3D cube: centrality, distinctiveness, breadth · axes registered: centrality, distinctiveness, breadth, depth, momentum · a board picks its own in knowledge/compare/braketool.cdmap (cut|x|y, cube|x|y|z); absent = the HBR defaults
Position map, two-dimensional cutOne bubble per player. Bubble area is breadth, the ring colour is momentum, the dashed lines are the category means, and both axes are fitted to the field of play with their tick numerals shown. Every value is repeated in the table that follows. 100 200 300 400 500 600 300 400 500 600 700 800 900 centrality (permil, fitted 100–600) distinctiveness (permil, fitted 300–900) mean 285 mean 627 Unconventional Aspirational Peripheral Mainstream Nishi, centrality 500, distinctiveness 761, breadth 380, depth 761, momentum 0 Single-plate, centrality 214, distinctiveness 750, breadth 71, depth 1000, momentum 0 Dual-plate ratchet, centrality 285, distinctiveness 375, breadth 71, depth 500, momentum 0 Wind-back kit, centrality 285, distinctiveness 583, breadth 95, depth 666, momentum 0 EPB scan tool, centrality 142, distinctiveness 666, breadth 95, depth 666, momentum 0 Nishi Single-plate Dual-plate ratchet Wind-back kit EPB scan tool

bubble area = breadth · ring = momentum (green rising, red falling, grey until day two) · dashed = category means · axes fitted to the field of play: centrality 100–600, distinctiveness 300–900 of 0–1000 permil (the full range put every player in one corner)
readability of the 2D cut, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 0 (a fact of the data: two players that close are that close) · data spread 680 permil of the plot · quadrant words unseated 0
text contrast, measured with wcag2-ratio (floors from contrast.conf), light theme: labels 16.24 (floor 4.50) · notes 16.24 (floor 4.50) · quadrant words 5.89 (floor 4.50) · tick numerals 5.89 (floor 4.50) · axis titles 5.59 (floor 4.50) · dark theme: labels 13.78 (floor 4.50) · quadrant words 5.55 (floor 4.50) · axis titles 5.97 (floor 4.50) · dark classes under their floor 0 (one figure serves both themes: a dark shortfall is a token to fix, never a class to hide) · classes refused under their floor 0 (a refused class is not drawn; the scale classes are measured, never hidden) · export: SVG PNG (receipt, rendered by the estate's own rasteriser from this page)
Position map, three-dimensional cubeThe same players in an isometric cube. Each axis is fitted to its own field of play and carries numerals on the floor grid and the vertical axis; each bubble drops a dotted line to its floor shadow so height reads as height. Values are in the table that follows. 100 200 300 400 500 600 300 400 500 600 700 800 900 0 100 200 300 400 500 centrality distinctiveness breadth Dual-plate ratchet: centrality 285, distinctiveness 375, breadth 71 EPB scan tool: centrality 142, distinctiveness 666, breadth 95 Wind-back kit: centrality 285, distinctiveness 583, breadth 95 Single-plate: centrality 214, distinctiveness 750, breadth 71 Nishi: centrality 500, distinctiveness 761, breadth 380 Nishi Single-plate Dual-plate ratchet Wind-back kit EPB scan tool
axes fitted: centrality 100–600 · distinctiveness 300–900 · breadth 0–500 permil · farther bubbles are painted first, nearer ones over them · the floor shadow is each bubble's (x, y) at height 0
readability of the 3D cube, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 0 (a fact of the data: two players that close are that close) · data spread 273 permil of the plot
Position map, small multiplesEvery pair of registered axes as one small cut. Each panel fits both axes to the field of play, the dashed lines are the category means, bubble area is breadth and the ring colour is momentum; the legend below names the colours. 100 600 300 900 distinctiveness vs centrality Nishi: centrality 500, distinctiveness 761 Single-plate: centrality 214, distinctiveness 750 Dual-plate ratchet: centrality 285, distinctiveness 375 Wind-back kit: centrality 285, distinctiveness 583 EPB scan tool: centrality 142, distinctiveness 666 100 600 0 500 breadth vs centrality Nishi: centrality 500, breadth 380 Single-plate: centrality 214, breadth 71 Dual-plate ratchet: centrality 285, breadth 71 Wind-back kit: centrality 285, breadth 95 EPB scan tool: centrality 142, breadth 95 100 600 400 1000 depth vs centrality Nishi: centrality 500, depth 761 Single-plate: centrality 214, depth 1000 Dual-plate ratchet: centrality 285, depth 500 Wind-back kit: centrality 285, depth 666 EPB scan tool: centrality 142, depth 666 100 600 480 520 momentum vs centrality Nishi: centrality 500, momentum 500 Single-plate: centrality 214, momentum 500 Dual-plate ratchet: centrality 285, momentum 500 Wind-back kit: centrality 285, momentum 500 EPB scan tool: centrality 142, momentum 500 300 900 0 500 breadth vs distinctiveness Nishi: distinctiveness 761, breadth 380 Single-plate: distinctiveness 750, breadth 71 Dual-plate ratchet: distinctiveness 375, breadth 71 Wind-back kit: distinctiveness 583, breadth 95 EPB scan tool: distinctiveness 666, breadth 95 300 900 400 1000 depth vs distinctiveness Nishi: distinctiveness 761, depth 761 Single-plate: distinctiveness 750, depth 1000 Dual-plate ratchet: distinctiveness 375, depth 500 Wind-back kit: distinctiveness 583, depth 666 EPB scan tool: distinctiveness 666, depth 666 300 900 480 520 momentum vs distinctiveness Nishi: distinctiveness 761, momentum 500 Single-plate: distinctiveness 750, momentum 500 Dual-plate ratchet: distinctiveness 375, momentum 500 Wind-back kit: distinctiveness 583, momentum 500 EPB scan tool: distinctiveness 666, momentum 500 0 500 400 1000 depth vs breadth Nishi: breadth 380, depth 761 Single-plate: breadth 71, depth 1000 Dual-plate ratchet: breadth 71, depth 500 Wind-back kit: breadth 95, depth 666 EPB scan tool: breadth 95, depth 666 0 500 480 520 momentum vs breadth Nishi: breadth 380, momentum 500 Single-plate: breadth 71, momentum 500 Dual-plate ratchet: breadth 71, momentum 500 Wind-back kit: breadth 95, momentum 500 EPB scan tool: breadth 95, momentum 500 400 1000 480 520 momentum vs depth Nishi: depth 761, momentum 500 Single-plate: depth 1000, momentum 500 Dual-plate ratchet: depth 500, momentum 500 Wind-back kit: depth 666, momentum 500 EPB scan tool: depth 666, momentum 500
Nishi Single-plate Dual-plate ratchet Wind-back kit EPB scan tool
10 panels over 5 registered axes, every pair once (the lower axis on x, the higher on y) · each panel fitted to its own field of play, first and last tick numerals shown · no labels in a small cut, the legend names the colours; the grade below reports the mark terms only (MM summed over the panels, spread averaged)
readability of the small multiples, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 7 (a fact of the data: two players that close are that close) · data spread 562 permil of the plot
PlayerQuadrantcentralitydistinctivenessbreadthdepthmomentumRows heldDays on spineFirst seen
NishiAspirational5007613807610 since 2026-09-237102026-09-15
Single-plateUnconventional2147507110000 since 2026-09-231102026-09-15
Dual-plate ratchetMainstream285375715000 since 2026-09-232102026-09-15
Wind-back kitMainstream285583956660 since 2026-09-232102026-09-15
EPB scan toolUnconventional142666956660 since 2026-09-232102026-09-15
DayMatrix rows reviewedPlayers recorded
2026-09-15145
2026-09-16145
2026-09-17145
2026-09-18145
2026-09-19145
2026-09-20145
2026-09-21145
2026-09-22145
2026-09-23145
2026-10-08145

players 5|matrix rows 14|feature mass 14|centrality mean 285|distinctiveness mean 627|axes 5|spine days 10 (shown 10)|rows written today 0|readability defects 2D 0 cube 0|spine knowledge/status/cdmap/braketool.spine

How to read this evidence. A Nishi source mark records whether the named symbol is declared in the selected source file. It does not establish working behavior or accepted delivery. A watching tag names an expected source entry; discovering it updates source coverage only. A dark tag means the file exists but the named symbol was not found: inspect the source and contract before assuming the capability is missing or renaming code. Peer codes are authored assessments; unassessed means no comparison is established, not absence. Qualification, deployment identity, runtime observations and acceptance must carry their own evidence. Adoption records the catalog's observed path through source, build, promotion, registration and invocation; libraries use importer evidence and gates use declared execution surfaces. A full catalog path does not establish quality, freshness or a successful user outcome. Partial and unknown states retain their stated next action. Census stamps: importers asof 1790637268, gate census asof 1790104131 (unix seconds; -1 = census absent).

Capability matrix — measured against source

◉ authored stronger claim; source present● present◐ partial○ absent? unassessed; excluded from relative comparison · click any capability for its evidence

Peer cell coverage: authored assessed 56, unassessed 0. Authored assessments are not verified outcomes.

CapabilityNishiSingle-plateDual-plate ratchetWind-back kitEPB scan tool
PRESS
Compress a single front pistonOpen — watching runtime/nx_braketool.nx : bt_single_press, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. The commodity job -- forum practice uses a C-clamp and the old pad [gjthread]. Our tool must not lose this case while winning the dual case
watching bt_single_press
Pros none measured yetCons behind Single-plate (leads), Dual-plate ratchet, Wind-back kit; open contract; expected source declaration not established
○◉●◐○
Compress dual and quad pistons EVENLY, no piston cockingOpen — watching runtime/nx_braketool.nx : bt_even_press, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. The dual-plate ratcheting class pushes both pistons with paired boards [presspicks] [pistonpicks] but publishes no evenness proof. Contract = even pressure BY GEOMETRY, proven by a displacement-delta gate on a dual-piston fixture
dossierwatching bt_even_press
Pros none measured yetCons behind Dual-plate ratchet; open contract; expected source declaration not established
○○◐○○
Rear caliper wind-back, rotate while pressingOpen — watching runtime/nx_braketool.nx : bt_windback, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. Wind-back cube kits own the rear rotate-and-press case; the dual-plate class does not rotate. Contract = a combined rotate-press head so one tool spans front and rear rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them
watching bt_windback
Pros none measured yetCons behind Wind-back kit (leads); open contract; expected source declaration not established
○○○◉○
Clamp-force indication and overload refusalOpen — watching runtime/nx_braketool.nx : bt_force_gauge, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. Nobody in the hand-tool class shows the force applied -- seal damage and bore scoring are invisible until failure [pistonpicks]. Contract = force indication with a declared ceiling and a mechanical overload refusal; the exceed this product is built around
watching bt_force_gauge
Pros none measured yetCons open contract; expected source declaration not established
○○○○○
SAFETY
EPB service-mode workflow, motor retract before pressOpen — watching runtime/nx_braketool.nx : bt_epb_flow, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. EPB calipers must be put in service mode by a scan lane before any press -- forcing the piston damages the motor or mechanism [foxwellepb] [epbreset]. We do not build a scan tool; the contract is the workflow card bound to the tool: model-family rows as DATA naming when a scan lane is REQUIRED
dossierwatching bt_epb_flow
Pros none measured yetCons behind EPB scan tool (leads); open contract; expected source declaration not established
○○○○◉
Fluid backflow and reservoir overflow guidanceOpen — watching runtime/nx_braketool.nx : bt_fluid_model, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. Pressing pistons returns fluid to the reservoir; an overfilled reservoir overflows and contaminated fluid is pushed back through the ABS body. Contract = the fluid-volume model per caliper class with an open-bleeder decision row rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them
watching bt_fluid_model
Pros none measured yetCons behind EPB scan tool; open contract; expected source declaration not established
○○○○◐
DESIGN
Thread mechanics and clamp-force modelOpen — watching runtime/nx_braketool.nx : bt_force_model, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. The design organ under the even-press and force-gauge rows: screw pitch, friction and plate stiffness to force at the handle, proven against a load-cell fixture gate
dossierwatching bt_force_model
Pros none measured yetCons open contract; expected source declaration not established
○○○○○
Outcome-to-capability decompositionSource present; authored stronger claim: pd_parse in runtime/_hdl_build/nx_product_decompose.nx, verified at emit. The estate product decomposer maps the named outcome onto required capabilities and gaps -- no tool vendor ships its analysis lane Adoption: REGISTERED-DARK — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked).
not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
Pros Source symbol found; stronger capability claim is authored; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan toolCons not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
◉○○○○
Digital-twin fabrication lane, STL to G-codeSource present; authored stronger claim: sl_slice_stl in runtime/_hdl_build/nx_slicer_lib.nx, verified at emit. Printed prototype plates and fixtures come off the sovereign slicer before any machined steel Adoption: LIB-WIRED importers=2 nonval=1 — fully adopted (top of its ladder).
Pros Source symbol found; stronger capability claim is authored; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan tool; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
◉○○○○
BUSINESS
Landed-cost and tariff corridor pricing for the BOMMeasured: lc_calc exists in runtime/_hdl_build/nx_landed_cost.nx, verified at emit. Tool steel and hardware priced through the sovereign landed-cost engine with corridor ranking Adoption: RUN-BY:clock — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan tool; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○
Sourcing-mix and reshore-path pricingMeasured: sp_mix exists in runtime/_hdl_build/nx_sourcing_path.nx, verified at emit. The domestic-vs-import BOM path priced step by step -- the buy-vs-build instrument for the manufacturing decision Adoption: REGISTERED-DARK — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked).
not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
Pros Implementing source symbol found; runtime acceptance separate; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan toolCons not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
●○○○○
Domestic supply-chain and good-jobs case for the manufacturing decisionMeasured: sc_domestic_permil exists in runtime/_hdl_build/nx_supplychain_case.nx, verified at emit. Origin class, energy risk, single-source and value roll into weighted risk and domestic-content permil -- the case a made-in-America tool line leads with Adoption: LIB-WIRED importers=3 nonval=2 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan tool; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○
Go-to-market channel engine (facade live in an adjacent domain)Measured: gtm_channel_best exists in runtime/nx_gtm_svc.nx, verified at emit. The GTM facade ranks channels per product today in the supplement domain -- tool retail and pro-channel rows are a data admission, not new code Adoption: REGISTERED-DARK — PARTIAL: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked).
not adopted: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
Pros Implementing source symbol found; runtime acceptance separate; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan toolCons not adopted yet: callable, authorised, completed MCP invocation not established by supplied journal window; lifetime history unknown (direct execution may be recorded elsewhere; this scan does not establish lifetime use); no execution surface runs it either (clock, cron, daemon, roster, actlog and surfaced forks checked)
●○○○○
EVIDENCE
Sovereign mirrored and pinned reference register for this fieldMeasured: knowledge/fetched/cmp_braketool exists in knowledge/compare/braketool.refs, verified at emit. Every rival claim on this page resolves to a mirror in the estate evidence store, content-pinned by hash and re-measured on every emit Adoption: ABSENT — PARTIAL: no source and no binary: this is a build contract, not a partial deploy.
not adopted: no source and no binary: this is a build contract, not a partial deploy
Pros Implementing source symbol found; runtime acceptance separate; ahead of Single-plate, Dual-plate ratchet, Wind-back kit, EPB scan toolCons not adopted yet: no source and no binary: this is a build contract, not a partial deploy
●○○○○
Rival-claim provenance. Every Yes, Best or Part mark in a rival column is a claim about someone else's product. A cited row carries a reference mark that resolves to a pinned mirror (the refs gate measures that); an uncited row is an observation read and is badged in its evidence until a reference lands. The badge is the receipt, never the proof: a mark proves a mirror exists, not that the mirror supports the code. The rows are counted below.
Rival claims, counted
ClassCountNote
rows with rival marks5rows carrying a Yes, Best or Part in a rival column
cited3a reference mark resolves to a pinned mirror
uncited2an observation read, badged until a reference lands
rows, summed5RECONCILED: the parts sum to the total 5

Delivery and evidence

Inspect risks, technical debt, rendered observations, experiments and references. Read scope and limitations alongside every result.

Risk register

RiskLikelihood x impactMitigation
Brake work is a safety domain -- a tool that damages a seal or an EPB actuator creates a braking failurepossible x severeBT3 encodes the scan-lane requirement as a refusal card [foxwellepb]; BT6 witnesses the force-ceiling refusal on real calipers; no article ships on partial coverage
A watch contract flips on symbol existence, so a stub reads greenpossible x highthe flip is the receipt, the rung gate is the proof
The commodity floor undercuts the priceprobable x mediumthe biz position is the measured spec, not price; M1 gates the manufacturing decision on real BOM numbers
On these two registers. Rows are declared in the domain's plan file and carry the debt id, which is the join key back to the sovereign debt plane — that plane, not this page, is the authority on state. Reconciling them automatically (the regen reading the plane and refreshing these rows) is a named, owed rung; until it lands, treat an id here as a pointer to look up, not a status to trust.
Honest verdict. The Aug-2026 hand-tool field, honestly: single-plate spreaders and plain C-clamps own the single-piston case at commodity prices and working-mechanic forum practice happily uses an old pad and a clamp [gjthread]. Ratcheting dual-plate presses -- the FIVE BANANAS pick of the 2026 review field [presspicks] and the TUTOOLS, BARTOO and OMT class beside it [pistonpicks] -- push paired pistons with matched boards, but none publishes force feedback or an evenness proof, and reviewers note the ratchet mechanisms need pressure on both plates before they act. Wind-back kits own the rear rotate-while-press case the dual-plate class cannot touch. And the electronic-parking-brake era moved part of the job into the scan lane entirely: an EPB caliper must be motor-retracted into service mode before any press, or the actuator and mechanism are damaged [foxwellepb] [epbreset]. The better double expander is therefore not a stronger screw. It is even pressure BY GEOMETRY, clamp-force indication with an overload refusal (the exceed nobody ships), a rear wind-back head so one tool spans the axle set, and an EPB workflow card bound to the tool -- each proven by its own gate before steel is cut, with the BOM priced through the estate landed-cost and sourcing engines.

Person · product · place — not yet measured for this domain

Every compare carries this layer. Declare knowledge/compare/braketool.ppp (rows surface|nishi or c1..c4|label|url|connect naming OUR live surface and each rival's front door), run nx_ppp_probe domain braketool, and this section fills itself on the next beat: the same ruler on both sides — privacy and CX (third-party hosts, tracker classes, cookies, security headers), design and longevity (design hygiene, computed WCAG contrast, render-blocking resources, unsized media, script weight, theme and motion queries), findability (landmarks, skip link, on-site search, breadcrumb, headings, internal links).

The field — discovered, not chosen

Rows written by nx_field_discover from braketool.seeds: the industry's own lists (Wikipedia wikitext, GitHub topics, awesome lists) read mechanically, every candidate counted across seeds. The matrix columns above are a SEAT'S pick; this band is the population they were picked from, and the stats line measures one against the other. A rival here is a lead, never a verdict — it earns a column when its capabilities are read and pinned.

Discovery receipt. One row per counter the run wrote, in the receipt's own order; the rival rows follow in their own table.
Field discovery, counted
ClassCountNote
seeds2
scanned2
fetched2
reused0
failed0
named2
candidates2
mentions2
capped0
RankRivalSeedsMentionsFirst seedKindLink
1Dual-plate ratchet11col1-dualnamedhttps://weldingresource.com/best-brake-caliper-piston-tool/
2EPB scan tool11col3-epbnamedhttps://premium-diagnostics.com.au/blogs/news/how-to-reset-an-electronic-parking-brake-epb-with-a-scan-tool

field candidates 2|shown 2 of 2|matrix columns in the field 2 of 4|discovered rivals with no column 0|malformed rows 0 (counted, never rendered)|read-capped 0

Exclusive and shared capabilities

One capability is graded on one board; every other board references it. The fleet duplicate census (nx_rivalcensus dupes, on the fleetdupes clock row) reads every board's matrix and names each capability graded as a row on two or more boards, with a home derived from evidence: rung when exactly one board's plan contracts the symbol (that board is starred), gates when no plan contracts it and exactly one board's executed gate map runs the organ's gate (that board is plussed), ambiguous when several boards carry the deciding evidence (a decision for their seats), and none when no evidence decides it, with the reason beside it: unmapped (no board of the duplicate declares a gates map; declare the maps) or unproven (a map exists and runs none of the organ's gates; gate the organ on its proving board, or declare it a shared library by policy). A home elsewhere means this board should carry an @xrow reference to the home board's row rather than a graded row of its own; a home here means the other boards should. The table is this board's slice of one estate-wide census: the shape is shared, the rows are the board's.

This board grades 14 capabilities: 8 exclusive to it and 6 shared with other boards. Shared rows on this page: 6 = home here 0 + home elsewhere 1 + ambiguous 0 + undecided 5 + refused 0 (partition 6); undecided = unmapped 2 + unproven 3 + unevidenced 0; homonyms 0; since the previous census: new 0, resolved 0. Census FRESH age_s=6686.

CapabilityOrganBoards grading itHomeRuleEvidenceStanding on this board
lc_calcnx_landed_cost.nxgrowth*, appliancemove, braketool, soilscience, alignbiz, carflip, butterchurn, phototwin, tradecompliancegrowthrungplanhome elsewhere
adopt: @xrow growth|lc_calc|home by rung (fleet duplicate census)
pd_parsenx_product_decompose.nxappliancemove, braketool, soilscience, alignbiz, realestate, supimacotton, butterchurn, phototwin—noneunprovenundecided
sl_slice_stlnx_slicer_lib.nxappliancemove, braketool, butterchurn—noneunmappedundecided
sp_mixnx_sourcing_path.nxappliancemove, braketool, supimacotton—noneunmappedundecided
sc_domestic_permilnx_supplychain_case.nxappliancemove, braketool, realestate—noneunprovenundecided
gtm_channel_bestnx_gtm_svc.nxappliancemove, braketool, soilscience, alignbiz, carflip, supimacotton, butterchurn, phototwin—noneunprovenundecided

Gaps from the record — what the estate does that no board carries

The record census (nx_goalmap record) reads the invoked-tool population and every plan queue row and files each organ or directive that NO matrix, plan or gates row names. A row here is a callout the boards missed: adjudicate it onto a board or declare it infrastructure. Census state STALE (age 1395791 s), sources read 4 of 7 declared — a BLIND census is a FLOOR: unread sources can only add rows.

kindnameboardsourceevidence

rows shown 0|this board's directives 0|estate-wide un-boarded organs 452 (listed in full on /compare/ecosystem)|census rows 639|malformed 0 (counted, never rendered)

References

Beyond a link list. Every reference below resolves twice — the publisher's copy and, where banked, the estate's own non-rottable library mirror with a content pin — and carries its evidence class plus the exact claim on this page it grounds. Keyed marks like [key] in the matrix notes jump here. A dash means honestly absent, never assumed.
  1. [presspicks] WeldingResource. Best brake caliper press tool, updated 2026 -- review field naming the FIVE BANANAS dual push-board press with adjustable spreader as the standout for evenly pushing pistons on multi-piston calipers. publisher · read in our library knowledge/fetched/cmp_braketool_presspicks.html · pin he3109e0631d85afee51873e9c091c7e9c65734823afc224ae1f0409cfc02a0c4 · accessed 2026-08-19 · mirrored-indexGrounds: The dual-piston even-press row: the best of the incumbent dual-plate class, and what it still does not prove.
  2. [pistonpicks] WeldingResource. Best brake caliper piston tool, updated 2026 -- the wider ratcheting-press field (TUTOOLS, BARTOO, OMT class) with user notes on ratchet mechanisms needing pressure on both plates to act. publisher · read in our library knowledge/fetched/cmp_braketool_pistonpicks.html · pin h2b704a294b4a8f0253ac84554cbf19d347dc29e8f3301aa73f8b0e297c817003 · accessed 2026-08-19 · mirrored-indexGrounds: The even-press and force-gauge rows: the incumbent class publishes no force feedback and no evenness proof.
  3. [foxwellepb] Foxwell. How the scan tool releases the electronic parking brake. Vendor technical blog -- the EPB motor must be commanded into service mode to retract the piston before pad service; forcing it damages the motor or caliper mechanism. publisher · read in our library knowledge/fetched/cmp_braketool_foxwellepb.html · pin h34624d2b27bd31171e3946fa8fa719553d56c3042b7fde43c22573984072b51c · accessed 2026-08-19 · vendor-docGrounds: The EPB service-mode row: why part of the modern job lives in the scan lane and the tool must carry the workflow card.
  4. [epbreset] Premium Diagnostics Australia. How to reset an electronic parking brake with a scan tool. Vendor technical blog -- EPB service and retract functions, service position confirmation, and the re-initialise step after pad fitting. publisher · read in our library knowledge/fetched/cmp_braketool_epbreset.html · pin h8c205809413846e216e794d8ed4eea5048994f3cf722709cc4438e2e13a51029 · accessed 2026-08-19 · vendor-docGrounds: The EPB workflow row: the full service-mode sequence the bt_epb_flow card must encode as data.
  5. [gjthread] The Garage Journal forum. Brake caliper tool thread -- working-mechanic practice on caliper compression: single pistons handled with C-clamps and the old pad; tool preferences argued from shop experience. publisher · read in our library knowledge/fetched/cmp_braketool_gjthread.html · pin h3b0ca7e1fa8aafa614c2808cdaaa2a2858b1931243b6825213bd423ce6ee2c0f · accessed 2026-08-19 · mirrored-indexGrounds: The single-piston row: the commodity case our tool must not lose while winning the dual case.

generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/braketool.matrix · source checks show implementation presence; runtime and user-outcome evidence are reported separately · JavaScript supports page controls