Skip to content

Angelguirao/projects

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

23 Commits
 
 
 
 

Repository files navigation

Projects

Angel Guirao — product-minded full-stack engineer building tools for knowing, deciding, and shipping without outsourcing judgment to platforms or copilots.

This repository is the map: how my projects relate, what each one owns, and where to look first. Ten sibling repos beside this folder — not a monorepo. Compose mature open source. Own the glue.


Start here

Link What it is
Mesh angelguirao.com Felt rooms — problems, identity, projects, connection
Footnotes angelguirao.com/wiki Concepts from reading, distilled for strangers
Holzen holzen.app Shipped product — pause before capital moves
AI-Native Product Building handbook Living handbook — decisions for building with AI

The mesh is how it feels. Footnotes are what I know in public. Holzen is what I ship to users. The handbook is what I teach.

How code should look from the inside: holzen’s application architecture is the product reference. Stack constitution and repo seams live in private/local docs (docs/, brain/BOUNDARIES.md) — not published from this repo.


The through-line

I read and clip. Ideas compile into a wiki (folio). A personal agent (steward) routes attention across the day. Selected work becomes exhibition on the mesh (tbd). Products that earn users get their own repo (holzen). Experiments start in a sandbox (bench) and graduate or die. Open source gets composed; the seams between repos are mine.

flowchart TB
  subgraph know["Knowing"]
    LIB[codex · library]
    FOL[folio · brain]
    LIB --> FOL
  end

  subgraph decide["Deciding"]
    AG[agents · specs]
    ST[steward · personal-agent]
    FOL <--> ST
    AG --> ST
  end

  subgraph show["Showing"]
    MESH[tbd · mesh + wiki]
    FOL --> MESH
  end

  subgraph ship["Shipping"]
    HOL[holzen]
    CHR[charter · venture-builder]
    REL[relay · dispatch]
    CHR --> REL --> HOL
  end

  subgraph prove["Proving"]
    LAB[bench · lab]
    MON[anchor · money]
    LAB --> FOL
    LAB --> ST
    MON --> FOL
  end
Loading

Reading infolio holds what's true enough → steward routes the day → tbd exhibits what earns visibility → holzen (and future ventures) ship to the world. bench tries OSS first; relay and charter connect venture work.


The projects

Product names are what I call them day to day. Folder names are the git repos.

Knowing

folio · brain/ · active
Markdown wiki for what I read and think — capture, search, compile, publish footnotes when an idea is ready to meet the world.

codex · library/ · building
Home for books and PDFs that feed folio — keep what matters locally, sync the rest into notes.

Deciding

steward · personal-agent/ · active · private repo · PersonalOS →
Always-on steward on VPS — PersonalOS is the primary surface (desks, feed, chat). Telegram is pocket capture overflow.

agents · agents/ · active · private repo
Portable agent specs — cloud runtimes only (VPS, Vercel). Specialists are background engines; you talk to steward on PersonalOS.

vocation-desk · vocation-desk/ · active
Evidence-first apply pipeline (career-scout engine) — VPS cron + PersonalOS /os/career. No local agent runtime.

Showing

tbd · tbd/ · active · mesh →
Public exhibition — mesh rooms and footnotes only. /os and /wiki/inner redirect to PersonalOS.

AI-Native Product Building · ai-native-product-building/ · active · handbook →
Living handbook — decision frameworks for building products when AI changes every step. Chapters in MDX; drafts start in brain.

Shipping

holzen · holzen/ · active · holzen.app →
Deliberate friction before capital moves — a ritual that keeps investor decisions human-sized.

charter · venture-builder/ · building
Constitution for side ventures — gates, templates, and rules for what gets built, promoted, or killed.

relay · dispatch/ · building
Background jobs and webhooks for repeatable work — product cycles, agent maintenance, venture ops.

Proving

bench · lab/ · active
Sandbox for open source — Bitcoin tooling, evals, agents, and upstream trials before they graduate into the stack.

anchor · money/ · building
Self-custody Bitcoin infrastructure — compose, regtest, and runbooks for running my own node.


Connect

About

Public stack map — mesh, footnotes, Holzen, and nine sibling repos (compose OSS, own the glue)

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors