Team Ai
9 results

chief-engineer

kylebrodeur /chief-engineer-ledger Microfactory Node: 3D Printer (Lesson Ledger) The compounding memory of Microfactory Node: 3D Printer, a small local Gemma that learns 3D printing job by job. Each row is one durable lesson keyed to the conditions it was learned in. The node retrieves from this ledger before every print, so job N+1 starts smarter than job N. This is the knowledge that usually lives in one maker's head and dies with the shop. Here it persists, and anyone can read it. Project: Live · Code.… See the full description on the dataset page: https://huggingface.co/datasets/kylebrodeur/chief-engineer-ledger.n<1K0 likes40 downloads4mo agoHugging Facekylebrodeur /chief-engineer-finetune-activity Chief Engineer — fine-tune activity trace A timestamped log of the LoRA fine-tune pipeline for Microfactory Node: 3D Printer (Gemma 4 E4B): dataset generation, training, evaluation, quantization, and publishing to HF Hub + ollama.com. One row per event. Schema: timestamp, action, event, details. Sibling: the build activity trace kylebrodeur/chief-engineer-build-activity. Project: node.microfactory.space · Code: github.com/kylebrodeur/microfactory-node. textn<1K0 likes24 downloads4mo agoHugging Facekylebrodeur /chief-engineer-deliberation Chief Engineer — Deliberation Traces Turn-by-turn multi-persona deliberation from The Chief Engineer, a small local Gemma agent built for the HF Build Small hackathon (Backyard AI). Where the lesson ledger records what the agent learned, this records how it reasons: the argument between the personas on each job. It grows two ways: a reproducible static export (make deliberation) and live turns logged on every run of the Space (gated on HF_TOKEN; config + agent reasoning only… See the full description on the dataset page: https://huggingface.co/datasets/kylebrodeur/chief-engineer-deliberation.tabulartext-generationn<1K0 likes23 downloads1mo agoHugging Facebuild-small-hackathon /chief-engineer-field-log Microfactory Node: 3D Printer (Field Log) Every interaction on the live node appends one row here: every build, second opinion, simulated print, iteration run, and recorded outcome. It is the node's field notebook, written as people use it, so the craft keeps accumulating past a single maker's bench. Logging is gated on a write token and silently does nothing without it. What is and isn't here Job configuration and outcomes only. No personal data. No uploaded mesh… See the full description on the dataset page: https://huggingface.co/datasets/build-small-hackathon/chief-engineer-field-log.0 likes22 downloads4mo agoHugging Facekylebrodeur /chief-engineer-build-activity Chief Engineer — build activity trace A timestamped log of building Microfactory Node: 3D Printer (HF Build Small hackathon): restructures, bug fixes, deploys, and review passes. One row per event. Schema: timestamp, action, event, details. Sibling: the fine-tune activity trace kylebrodeur/chief-engineer-finetune-activity. Project: node.microfactory.space · Code: github.com/kylebrodeur/microfactory-node. textn<1K0 likes19 downloads4mo agoHugging Facejhamel /alpaca-chief-engineer-preliminary-designtextn<1K0 likes1 downloads3y agoHugging Face