IntentForce · governed AI work · public evidence
AI-governed CAD and electronics development
IntentForce governs delivery from business need and scope to the right technical workflow, verification, documentation and safe handover. Finnandre performs the end-client technical delivery; IntentForce keeps intent, agents, evidence and decision boundaries connected.
Designed with OpenAI Codex. AI does not replace engineering responsibility or physical verification.
Intent
What is being built, for whom, within which boundaries, and what must be true at completion?
Execution
The right native tool, the right source basis and one clear owner for each writing task.
Evidence
Files, checks, date, hashes, unknowns and reversible publication—without turning assumptions into facts.
How governance works
Meta-intelligence in practice: govern how intelligence is used
An ordinary agent can be told to “make an enclosure” or “design a PCB”. The governing layer first decides what kind of problem it is, which sources are authoritative, which native tool must perform the work, which checks are relevant, who owns the change and where the workflow must stop.
For this series, the brief and hardware requirements became explicit dimensions and access needs. Official drawings and datasheets were used where necessary. Codex performed bounded operations in native FreeCAD and KiCad, while scripts and human review checked file structure, geometry, nets, recorded DRC, exports and publication boundaries.
Sources before shape
Dimensions, pin functions and mechanical constraints come before an attractive final image.
Native work
FCStd and KiCad project files preserve more intent than screenshots and meshes alone.
Bounded checks
A passed software check is described as exactly that—not as physical certification.
Public
What others should be able to inspect
- Exact public GitHub history and licence boundaries.
- 19 native FreeCAD files across 15 case projects.
- Case-only STEP/STL, images, notes and hash manifests.
- Two editable KiCad projects with schematics, PCBs, BOMs, netlists, Gerbers, drills and STEP.
- 16 public release films and one YouTube-only film, each mapped to relevant source.
Private
What must not travel with the evidence
- Customer names, private relationships and internal topology.
- Keys, tokens, cookies, local paths or operational receipts.
- Third-party CAD files without proven redistribution rights.
- Raw working material not required to inspect the public claim.
Controlled evidence
Independent readback of the public package
On 12 October 2026, all 19 FCStd files were individually downloaded from the exact public commit, opened and recomputed in native FreeCAD. The final base and lid objects were checked as valid single solids without resaving the files.
The original 15 MP4 files were anonymously downloaded and checked on 12 October. The new 600-second file was published on 13 October with exact size 24,468,956 bytes and SHA-256 36e50339378d485888e99282146dba78f6cee45e7d6a15c356c44fe37dfe8331. The public GitHub digest matches. The Pulse film is YouTube-only; its archived master was not unnecessarily restored.
Evidence boundary: File readback, recorded DRC and topology checks are software evidence. They do not replace physical fit, power-up, thermal/RF testing, fabrication, compliance or certification.
Controlled publication
One owner, backup, verification and rollback
The public package was sanitised before publication. The GitHub repository and release were then verified anonymously. Website pages are deployed with bounded backups, precondition checks and rollback. Social publication remains separately owned so that two agents cannot mutate the same schedule.
OpenAI Codex is credited as a development, automation and verification tool. This is an independent Finnandre/IntentForce project and does not imply endorsement by OpenAI, FreeCAD, KiCad or any hardware vendor.
Client-oriented delivery
The complete package without confusing promises and evidence
The workflow may include requirements and a fast working proof, electronic schematic, PCB, BOM, Gerbers and drills, editable enclosure, firmware or controller, local web and MQTT integration, narrated technical documentation, agreed verification and handover. Finnandre is the route to the concrete technical service. IntentForce is the governance layer for business outcomes, method selection, agent boundaries, human review and evidence.
When a project can be documented publicly, delivery can also include SEO, AEO, GEO and AI visibility: useful crawlable pages, direct answers, consistent facts, sources and correct attribution. We do not manufacture references, customers, outcomes or authority, and we do not guarantee rankings, indexing or AI citations.
Questions and answers
How does IntentForce differ from Finnandre here?
Finnandre provides the technical end-client delivery and files. IntentForce governs intent, method selection, agent boundaries, evidence, review and safe handover.
Can this be used for customer projects?
Yes, but the verification plan must match the real requirements, vendor data, responsibilities, licences, test environment and expected deliverables.
Does the workflow guarantee a correct physical product?
No. It makes decisions and software checks more inspectable. Physical engineering still requires relevant competence, prototypes, measurements and any required approvals.