Technical Docs
Implementation-level documentation for selected systems, libraries, and technical projects in this portfolio.
Project Atlas maps evidence; Builder Journey maps practice evolution. This area explains implementation depth where real documentation exists.
Published documentation
Each entry below opens an existing documentation set. Source links remain secondary to the reading path.
Project documentation
Local setup, data, notebooks, model topology, pipeline, architecture, results, and local serving.
NLP · ML · MLOps
Scope. Atlas evidence includes local execution and a sanitized cloud blueprint; no current production deployment is claimed.
Project documentation
Synchronized project README, technical documentation, reports, and release notes for the published snapshot.
ML · MLOps · AI-native products · Multicloud
Scope. Frozen portfolio evidence boundary remains tied to v0.4.0-alpha.1.
Library reference
Package overview plus synchronized link prediction, QAP, ERGM/STERGM approximation, methodology, examples, notebooks, and releases.
Python · Network statistics · Applied mathematics · Data science
Scope. Atlas context describes 2026 Python network-statistical software with explicit approximation boundaries.
Library reference
Getting started, API overview, architecture, examples, contributing guidance, and releases for the pure-Lua statistics library.
Lua · Statistics · Simulation
Scope. Strategic Builder Journey bridge in Atlas governance; not absorbed into the Liasoft collection.
Library reference
Getting started, examples, mesh behavior, API reference, architecture, and releases for the Gideros Lua utility.
Lua · Gideros · Creative coding
Scope. Creative Roots evidence inside the main portfolio; not a current product showcase.
Field guide
Independent visual field guide covering FDE role framing, delivery loops, capability pillars, depth tracks, learning paths, tradeoffs, and source provenance.
Forward Deployed Engineering · Technical Delivery · Systems / Cloud / Data / AI
Scope. Editorial synthesis / field guide only. Technical Docs publication depth does not upgrade Project Atlas evidence classification and is not proof that every described FDE activity was personally executed.
Portfolio context
Technical documentation can explain how a system works without changing its Project Atlas classification or its place in the Builder Journey.