• P1Start
  • More resources
Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
P1Start platform documentation
P1Start platform documentation
  • Tutorials
    • Getting started
  • How-to guides
    • Build and run (stub)
  • Reference
    • Developer platform index
    • SDK contract
    • Dynamic linking status
    • P1SCode status and scope
    • P1SCode architecture
    • P1SCode modules and std
    • P1SCode language guide
    • P1SCode language reference
    • P1SCode toolchain workflow
    • SDK + P1SCode v0 release notes
    • User virtual address layout
    • Userspace keyboard input (ps2d)
    • Threading model
    • Coverage matrix (subsystems × code × docs)
    • Legacy HTML bundle (pre-Sphinx)
    • WM v1 platform roadmap
    • PTY v1 design
    • Launch paths
    • PIXEL currency (PXL)
  • Explanation
    • Documentation map
    • System architecture
    • Foundation debt ledger
    • Terminal stack
  • Canonical contracts
    • Boot and init
    • Contributing to newdocs/
    • Doom / id Tech 1 Renderer Implementation Roadmap (P1Doom)
    • Dynamic linking ABI — code index (curated)
    • P1Start ecosystem philosophy (canonical)
    • ELF / PE loading (kernel)
    • File types, MIME, and the “open” pipeline — P1Start
    • Game engine architecture — Phase 0 contracts (P1Start)
    • IPC broker — SystemBroker
    • IPC wire — message_type index (curated)
    • Keyboard input, layouts, and text (US QWERTY today — UTF‑8 later)
    • Lua scripting architecture (P1Start)
    • Media types (MIME) on P1Start
    • Memory and address spaces
    • Networking architecture — contract & north star
    • Networking overview
    • P1SCode IDE / SDK / CLI toolchain
    • P1SCode — M1 product contract (P1SCode on P1Start)
    • Process lifecycle — birth, execution, death
    • RegCube — reference (hives, keys, syscalls, persistence)
    • Scheduler and SMP
    • Settings control pattern (p1-xxxsvc + xxxctl + GUI)
    • Sphinx reconciliation matrix (platform-docs vs canonical newdocs)
    • Staging and ramdisk
    • Syscalls reference (curated)
    • System architecture — P1Start (current)
    • Time and clock architecture
    • TLS and certificates
    • Userland matrix
    • VFS and filesystem
    • WM surface lifecycle — Create → Present → Destroy
Back to top

Explanation¶

Background and reasoning: how subsystems fit together, known constraints, and engineering history.

  • Documentation map
  • System architecture
  • Foundation debt ledger
  • Terminal stack
Copyright © 2026, P1Start contributors
Contents
  • Explanation