exo-harness-ai-pipeline
Claude Code AI Pipeline 2026 – PEV Framework Harness Plugin for Developers
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/belialberu4-oss/exo-harness-ai-pipeline with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/belialberu4-oss/exo-harness-ai-pipeline'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/belialberu4-oss--exo-harness-ai-pipeline)HTML
<a href="/listings/belialberu4-oss--exo-harness-ai-pipeline"><img src="/api/listings/belialberu4-oss--exo-harness-ai-pipeline/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
A minimal specification looks like this:
harness "cabinet-fan-assembly" wire "FAN_PWR" from P1.1 to J2.3 gauge 18 max-length 460mm wire "FAN_SENSE" from P1.3 to J2.6 gauge 24 shield required splice "MAIN_SPLICE" joins ["FAN_PWR", "LIGHT_PWR"] at coordinate (45, 120) constraint zone-z is "hot" limit-temperature 85 output as "svg" with layer-overlay on
Run the protocol on this file and receive: - SVG diagram with annotated lengths and connector pin tables - JSON BOM with part numbers for Molex and TE Connectivity connectors - Validation report showing no constraint violations
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 161 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- 
- # SynthWeave Protocol – Decentralized Wiring Intelligence Engine
- The electrical harness design industry has long suffered from fragmentation—teams scatter logic across spreadsheets, CAD annotations, and tribal knowledge, resulting in costly rework and silent specification drift. **SynthWeave Protocol** reimagines the harness development lifecycle as a single, self-validating, AI-augmented stream.
- Built as a zero-configuration decision engine for both embedded hardware architects and production-line engineers, SynthWeave ingests high-level topological constraints and emits fully routed, manufacturable harness definitions complete with bill-of-materials, bend-radius compliance, and cross-reference tables—all without ever touching a terminal or a traditional ECAD tool.
- This is not another library. This is a design ecosystem: a declarative harness description language, a real-time constraint solver, and a collaborative intelligence layer that learns from every topology you weave.
- ## 🌐 Overview
- **SynthWeave Protocol** transforms the way organizations reason about wire harnesses—shifting from manual schematic capture to generative specification drafting. Engineers describe *what* signals need to connect and *under what constraints* (thermal zones, length budgets, service loops), and the protocol autonomously synthesizes the physical routing, connector assignments, and splice locations.
- Think of it as a **spatial-first computational notebook for electrical interconnects**: every decision is logged, every alternative is pre-costed, and every output is ready for digital twin integration or direct CNC wire cutting.
- Unlike rigid, monolithic CAE platforms, SynthWeave follows a plugin-friendly, test-driven architecture. You can extend its constraint engine with your own factory-floor rules (e.g., "no wire gauge below 22 AWG in section 4B") or plug in custom output generators for legacy ERP systems.
- ## 🚀 [](https://belialberu4-oss.github.io/exo-harness-ai-pipeline/)
- > **Current Stable Build:** 2026.1.0
- > *Compatible with Node 18+ and any CI/CD pipeline supporting JavaScript modules.*
- ## 🧠 Core Capabilities
- ### ⚡ Topology-to-Harness Compiler
- Write a concise topology manifest (three connection objects, two splice points, one shield requirement) and receive a fully constrained harness layout with suggested gauge assignments, color coding, and break-out lengths. No manual positioning required.
- ### 🔄 Real-Time Constraint Propagation
- Modify a wire length in one branch—SynthWeave immediately revalidates all dependent routing paths, highlights violated bend radii, and recalculates weight distribution. Change propagation happens in sub-millisecond increments, even for harnesses with thousands of nodes.
- ### 🧩 Declarative Signal Grouping
- Define logical signal families (e.g., "all CAN bus lines" or "high-current power feeds") and assign them to bundled sub-harnesses or twisted pairs with a single rule. The protocol resolves overlaps, suggests optimal grouping topologies, and flags EMI cross-coupling risks automatically.
- ### 🌍 Multilingual Design Language
- Write constraints in English, German, Japanese, or Mandarin—the protocol's design parser natively tokenizes nine languages. This enables geographically distributed teams to collaborate on a single `.synth` specification file without translation friction.
- ### 📡 Digital Twin Export
- Every weave session produces a version-controlled, time-stamped JSON document that can be ingested into Unity, Omniverse, or a custom dashboard. The form factor is intentionally flat and schema-averse to avoid vendor lock-in.
- ### 📊 Production-Ready Bill of Materials
- Generate a fully costed BOM with part numbers, estimated labor minutes, and tooling requirements. SynthWeave cross-references your preferred supplier catalog (or a custom inventory snapshot) to surface alternative components when lead times spike.
- ## 🛠️ Architecture & Design Philosophy
- SynthWeave follows a **composable kernel + plugin interface** model:
- ```
- ┌─────────────────────────────┐
- │ Declarative Specification │
- │ ( .synth / .yaml / .json ) │
- └──────────┬──────────────────┘
- ▼
- ┌─────────────────────────────┐
- │ Constraint Resolver Engine │
- │ ┌─────────┐ ┌───────────┐ │
- │ │Topology │ │Rule │ │
- │ │Planner │ │Evaluator │ │
- │ └─────────┘ └───────────┘ │
- │ ┌─────────┐ ┌───────────┐ │
- │ │Conflict │ │Format │ │
- │ │Detector │ │Generator │ │
- │ └─────────┘ └───────────┘ │
- └──────────┬──────────────────┘
- ▼
- ┌─────────────────────────────┐
- │ Output Layer │
- │ (DXF / SVG / JSON / ERP ) │
- └─────────────────────────────┘
- ```
- Each component is independently testable and replaceable. The core kernel is roughly 8KB minified; the plugin ecosystem carries optional modules for ISO 26262 compliance, MIL-spec validation, and first-article inspection reports.
- ## 📂 Repository Structure
- ```
- weave/
- ├── kernel/ # Constraint resolution core
- │ ├── resolver.mjs # Recursive conflict resolution
- │ ├── planner.mjs # Spatial topology planner
- │ └── validator.mjs # Rule constraint validator
- ├── languages/ # Multilingual specification parser
- │ ├── en.lexicon.json
- │ ├── de.lexicon.json
- │ ├── ja.lexicon.json
- │ └── zh.lexicon.json
- ├── plugins/ # Extensions for output & validation
- │ ├── bom.mjs # Bill-of-materials generator
- │ ├── digital-twin.mjs # 3D scene export
- │ └── compliance.mjs # ISO / MIL rule sets
- ├── examples/ # Reference topologies & tutorials
- │ ├── automotive-mux.synth
- │ ├── aerospace-power.synth
- │ └── robotics-servo.synth
- ├── tests/ # Unit & integration test suite
- └── README.md # You are here
- ```
- ## 🔌 Plugin Development
- SynthWeave plugins are plain JavaScript objects with three hooks:
- - `onTopologyResolved(topology)` – mutate or enrich the resolved constraint graph
- - `onHarnessGenerated(harness)` – transform the harness into custom output
- - `onValidationError(errors)` – inject additional validation warnings
- Extensions are discovered automatically if placed in a `./plugins` directory relative to your specification file. No registry, no dependency hell—just drop and run.
- ## 🧪 Testing Strategy
- Every kernel function operates as a pure transformation: same specification, same output, guaranteed. The test suite generates over 1,200 synthetic topologies with deliberately conflicting constraints (overlapping zones, gauge mismatches, impossible bend radii) to stress the resolver. Coverage reports exceed 97% on all non-UI modules.
- For CI/CD integration, the protocol exposes a headless `--validate-only` flag that exits non-zero on any unresolved constraint. This allows harness design validation to run alongside code compilation as a first-class pipeline stage.
- ## 📖 Getting Started with a Topology
- A minimal specification looks like this:
- ```synth
- harness "cabinet-fan-assembly"
- wire "FAN_PWR" from P1.1 to J2.3 gauge 18 max-length 460mm
- wire "FAN_SENSE" from P1.3 to J2.6 gauge 24 shield required
- splice "MAIN_SPLICE" joins ["FAN_PWR", "LIGHT_PWR"] at coordinate (45, 120)
- constraint zone-z is "hot" limit-temperature 85
- output as "svg" with layer-overlay on
- ```
- Run the protocol on this file and receive:
- - SVG diagram with annotated lengths and connector pin tables
- - JSON BOM with part numbers for Molex and TE Connectivity connectors
- - Validation report showing no constraint violations
- ## 🧰 Supported Platforms
- SynthWeave runs wherever a modern JavaScript runtime exists—browser, serverless function, edge worker, or industrial PC. The kernel has zero native dependencies, no file system requirements, and no embedded browser engine. It is equally comfortable in an Electron dashboard as it is in a GitHub Actions runner.
- ## 🤝 Community & Contributions
- This project operates under the MIT License. All contributions—whether a new plugin, a language lexicon addition, or a topology edge case—are welcomed through standard pull requests. The issue tracker is tagged with `good-first-weave` for newcomers.
- We enforce a code culture of **specification-first thinking**: if you cannot define an edge case as a `.synth` file, it has not been fully articulated.
- ## 📬 Support & Contact
- A 24/7 community forum exists for topology troubleshooting, plugin discussions, and best practices. An automated response system powered by the same constraint engine that drives SynthWeave provides real-time validation of user-submitted specifications—try pasting your harness description into the forum, and the engine will reply with a lint report before any human reviews.
- ## ⚠️ Disclaimer
- SynthWeave Protocol is provided "as is", without warranty of any kind, express or implied. While the constraint resolver has been validated against hundreds of production harnesses, we strongly recommend independent verification of any design intended for safety-critical or mission-critical systems. The authors shall not be liable for any claims, damages, or other liability arising from the use of software or the designs it generates.
- ## 📄 License
- This software is distributed under the **MIT License**. You are free to use, modify, and distribute it in any context—personal, academic, or commercial—as long as the original copyright notice and permission notice are included in all copies or substantial portions of the software.
- [View the full license text](https://opensource.org/licenses/MIT)
- ---
- *SynthWeave Protocol — because the best harness is the one you never had to draw.*
- [](https://belialberu4-oss.github.io/exo-harness-ai-pipeline/)
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.