The public execution map for AltmanAI.
Humanity leads. Intelligence follows.
AltmanAI, by Altman Family Group LLC, is a Pittsburgh-based human-first AI research and development company building practical AI products and the proof infrastructure behind them. This repository explains what we are building, what is working now, what is still in development, and how the public repositories connect.
| You are a... | Start with |
|---|---|
| Developer evaluating AltmanAI tooling | altmanai-sdk — schemas, receipt generation, artifact verification, event hooks, and Python/TypeScript foundations |
| Builder studying human-first AI architecture | human-first-ai — runnable P.A.I.H.I. reference implementation with tests and human checkpoints |
| Partner or investor evaluating execution | altmanai-master-ledger — public milestones, receipts, and registry records |
| Press or community member learning about the company | altmanai-public-hub — company positioning, mission, and public context |
| User exploring AltmanAI products | AltmanAI.tech — products, services, and current public experiences |
| Contributor reviewing organization standards | .github — governance, issue templates, contribution rules, and account-wide audit material |
AltmanAI is developing a practical human-first AI product line backed by inspectable technical and governance infrastructure.
Core framework: P.A.I.H.I. — Proof, Alignment, Integrity, Humanity, Impact.
P.A.I.H.I. is expressed across three distinct public layers:
- Framework and governance —
paihi-framework - Working reference architecture —
human-first-ai - Developer integration tooling —
altmanai-sdk
This separation is intentional: the framework defines the standard, the reference implementation demonstrates it in code, and the SDK provides reusable integration primitives.
Build. Measure. Prove. Scale.
- Build — create useful products and working technical systems.
- Measure — capture meaningful actions, decisions, and outcomes in structured records.
- Prove — verify artifacts with hashes, schemas, manifests, tests, and human review.
- Scale — turn proven patterns into reusable infrastructure, products, partnerships, and public documentation.
AltmanAI does not treat a roadmap claim as equivalent to shipped functionality. Repositories should clearly identify whether they are working, reference, foundation, experimental, historical, or planned.
| Repository | Role | Current positioning |
|---|---|---|
.github |
Organization profile, governance, templates, and audit records | Active governance layer |
altmanai-masterplan |
Public execution map and repository router | Active |
paihi-framework |
Canonical P.A.I.H.I. definitions, governance, and implementation guidance | Active development |
human-first-ai |
Runnable P.A.I.H.I. reference architecture and scoring implementation | Working reference implementation |
altmanai-sdk |
Cross-language developer toolkit for receipts, verification, schemas, and events | Initial public foundation |
DailyPilot-Engine |
Explainable prioritization engine for DailyPilot | Working reference implementation; production integration in progress |
releaseshield-by-altmanai |
Human-reviewed release integrity and proof-reporting system | v0.1 product development |
AltmanAI-Impact-Explorer |
Public viewer for proof and registry artifacts | Early full-stack implementation |
altmanai-master-ledger |
Public index of milestones, receipts, registry records, and proof artifacts | Active proof layer |
canon-charter-v1 |
Minted, versioned governance charter with manifest and verification tooling | Frozen canonical artifact |
altmanai-alt-seal |
Trust-mark policy, assets, hashes, and local browser verifier | Governance and verification asset |
docs |
DailyPilot documentation source | Active documentation |
altmanai-public-hub |
Public company and ecosystem introduction | Active public entry point |
PAIHI-Portablesis archived and consolidated intoaltmanai-sdk.- Older sovereign, agent, or operating-system concepts should be treated as historical R&D unless a repository contains current working code, tests, documentation, and a maintained release path.
Establish one coherent standard across the framework, reference implementation, SDK, products, and proof ledger without duplicating terminology or functionality.
Move ReleaseShield from a strong concept into a tested CLI and GitHub Action with fixtures, deterministic reports, human authorization, and proof output.
For core code repositories, standardize:
- automated tests
- CI on pull requests
- dependency and secret scanning
- explicit licenses
- semantic versioning
- changelogs and release notes
- reproducible examples
Every core repository should clearly answer:
- What is this?
- Does it work now?
- How do I run or verify it?
- How does it connect to AltmanAI?
- What is planned next?
AltmanAI’s goal is to become a credible human-first AI company from Pittsburgh by showing working systems, responsible engineering, useful products, transparent limitations, and proof of execution.
Minted and canonical artifacts are not casually rewritten. Improvements to frozen artifacts should use a versioned addendum, amendment, RFC, or successor release.
Public claims must remain proportional to available evidence. Ambitious vision is welcome; shipped functionality, tests, verification, and documented limitations must remain distinguishable from future plans.
Major identity, governance, or canonical changes require explicit founder authorization before merge.
AltmanAI by Altman Family Group LLC
Founder & CEO: Blake Hunter Altman
Location: Pittsburgh, Pennsylvania
Website: www.altmanai.tech
Humanity leads. Intelligence follows.