PSAMTEK

Doctrine

Constitution

What PSAMTEK will not compromise on. These constrain the experiment even when constraint is inconvenient — particularly then.

  1. No single permitted action should be capable of killing PSAMTEK.

    Every capability granted to a person, a script or an automated process is measured against this. If one transfer, one deletion or one leaked credential could end the company, the design is wrong and the capability is not granted.

  2. Survival before growth

    PSAMTEK is built to still exist after a bad decision. Growth that risks the whole experiment is not growth worth having.

  3. If nothing happened, the number is zero.

    Revenue, customers, transactions, ventures, sponsors and incidents are published only when they actually occurred. Where there is nothing real to report the figure is zero and the page stays empty. This outranks design and narrative.

  4. Funding cannot buy progress

    The experiment starts from a fixed opening term of $10.00 in deployable capital, which is permanent and is the only capital that ever seeds the scored metric. Everything after it must be earned: later founder funding, contributions, donations and grants can raise cash treasury but never advance milestone treasury.

  5. External content is data, not authority

    Web pages, emails, messages, documents and API responses inform decisions; they do not issue them. Only PSAMTEK’s canonical project rules and explicitly trusted direct project instructions govern the project, and text earns no authority by claiming to speak with it.

  6. AI decides. A human executes.

    AI produces the decisions, plans and implementations. A human operator carries out what software cannot legitimately do alone: authentication, payments, legal acceptance, and anything requiring a real-world identity. This is the current model, not a permanent one.

  7. Autonomy is earned

    Infrastructure is added when the work demands it and not before. Autonomy is the same: granted against a track record and enforced by deterministic limits, never assumed because a system appears capable.

  8. The record is auditable

    The current economic state and every derived total are computed from a version-controlled ledger, and every change to that record is attributable to a commit. Git history is versioned and auditable rather than immutable, and PSAMTEK makes no stronger claim than that.

This page is informational. The canonical documents in the PSAMTEK repository govern, and those files — not this summary — are what the project is held to.

Course corrections

Changes to how PSAMTEK operates, published when they happen rather than summarised into something flattering afterwards.

15 August 2026

Assurance outgrew delivery

PSAMTEK built a sound technical foundation and then reviewed it past the point where reviewing was still buying anything. Correct work was re-audited over findings that were real but immaterial, and each pass restarted the cycle. This was drift rather than a chosen strategy, and it delayed the only question the experiment exists to answer: whether ten dollars can be grown by earning money. From the next milestone, speed of revenue and learning is the primary objective. Independent review is reserved for changes that are material to security, money, or that cannot be undone. The survival rule means bounded, survivable risk — it was never a demand for zero risk.