field-to-architect

Status: Public proof surface. Repo status: published public reference. Release status: not a product release. License review required.

Francisco Abner Rivera / Franzabner

CEO. Co-Founder. Mechanical, Electrical, and Autonomous Systems Architect.

Purpose

This repository documents the public-safe arc from field electrical work to systems architecture. It explains how field craft became architecture discipline: installability, traceability, physical constraints, commissioning habits, and review gates carried forward into mechanical, electrical, embedded, and AI-assisted engineering work.

Franzabner is Francisco Abner Rivera's personal public technical brand. This repo is part of that public surface. It is not the official company voice, not a civic-entity voice, and not a substitute for private employment records or sealed company implementation.

What This Repo Proves

Proof Area	Public Evidence
Field-to-architecture judgment	Field constraints are treated as design inputs, not afterthoughts
Cross-discipline vocabulary	Electrical, mechanical, embedded, and AI workflow language stay connected
Review posture	Every transition from field note to architecture decision needs a checkable boundary
Public-safe storytelling	Career context is presented without employer files, customer files, or protected project records

Public Proof Stack Connection

This repo routes readers back to the current Franzabner public proof stack:

• franzabner-proof-stack - public navigation and proof-routing spine.
• electrical-panel-dressing - electrical field discipline and documentation proof.
• public-pcb-review-checklist - PCB review discipline.

Technical Lanes Connected Here

• Mechanical / Fusion 360.
• Electrical / KiCad / PCB.
• Embedded / Pico / RP2350.
• Agents / harnesses.
• DGX / NVIDIA / fine-tuning.
• Omniverse / USD / 3D worlds.
• EPI / Hugging Face.
• Upwork proof routing after review.

Public / Private / Sealed Boundary

Public:

• Francisco Abner Rivera's public identity and technical brand.
• General career arc, field discipline, and architecture posture.
• Synthetic examples and public-safe proof routing.

Private or sealed:

• Customer files, employer project records, site identifiers, private source artifacts, sealed YOSO-YAi implementation, private infrastructure, credentials, and internal corpora.
• Any claim that a public story is a client case study or a deployed customer result.
• Any unrelated private account, civic entity, or company operating material.

Status Controls

• No fake release claims.
• No fake client or customer claims.
• No deployment or revenue claims.
• No hosted model, dataset, benchmark result, or Hugging Face artifact claim.
• License review remains required before changing license posture.

Closing

The field built the discipline.

The architecture keeps it visible.