Source-28 governance consolidation
COMPLETE
Replaced competing living-root governance with a 28-source canonical set and separate master handoff.
PRAXIS LIVES.
Paused by design. Authority sealed. Next gate waiting.
A public engineering record of what is proven, what is parked, what broke, what survived, and exactly where the build resumes.
- State
- PAUSED / FROZEN
- Verified
- Sep 8, 2026, 6:09 PM PDT
- Governance tag
- praxis-src28-v1
- HEAD
- 8b984b3638a134cbce9a0c8fa965fb2c4ab576ac
- Tree
- 62c37a6a3226e1458b384c597efa639413f57269
- Product parent
- praxis-p4e-v1
- Remotes
- 0
- Seal evidence
- 68697d9220bc36b0929a55f2a0a9c37ea34155f33176c6136025776ba12c9c1c
- Next gate
- P4F v2 — Actor + Membership Authorization Runtime Reconciliation
34/34P4C authorization-contract tests passed
27/27P4E PostgreSQL 18 tenancy/governance assertions passed
28Canonical governance sources sealed
0Git remotes at accepted boundary
Current freeze boundary
Verified from the accepted Source-28 seal evidence. The page itself is a side quest and does not advance product authority.
What PRAXIS is
A modular, multi-tenant, multi-user, role-aware, API-first, agent-native business operating platform whose first commercial wedge is CRM.
- Alien-tech experience; boring-reliable internals.
- Modular monolith first; scale by measured extraction.
- PostgreSQL is canonical operational truth; cache is disposable acceleration.
- Providers are adapters; PRAXIS owns domain identity and state.
- Security fundamentals are universal, not premium-plan features.
- Capabilities, entitlement, usage, release state and authorization are separate control layers.
- Agents are bounded principals with delegation, budgets, approvals and revocation.
- Evidence controls release. Code existence is not release authority.
Universal control chain
- Identity
- Tenant
- Actor
- Authorization
- Capability
- Entitlement
- Usage/Budget
- Release State
- Risk/Approval
- Execution
- Audit
- Metering
- Domain Event
Eight product planes
- CORE
- Identity, organizations, membership, teams, authorization
- FABRIC
- CRM objects, relationships, timeline, custom data
- COMMERCE
- PRAXIS billing plus tenant quotes, invoices, payments and reconciliation
- MEMORY
- Working, operational, summary, semantic and archive memory
- AGENTS
- Agent identity, delegation, tools, budgets, approvals and evaluation
- AUTOMATION
- Triggers, workflows, durable jobs, retries and approvals
- SIGNAL
- Reporting, scoring, anomaly/risk signal and next-best action
- CONNECT
- REST API, webhooks, service accounts, OAuth/integrations and MCP seams
Sealed history and preserved STOPs
PRAXIS keeps failed gates visible. A STOP is evidence, not something to rewrite out of the story.
- P0–P3CLOSED / SEALED
Earlier foundation phases are closed/sealed historical authority. The current Source-28 handoff preserves that history but does not enumerate every earlier sub-gate.
- P4APASS
Truth census completed and evidence recorded.
- P4B_R4 → P4BSSEALED
Contract candidate passed and was sealed.
- P4C_R2 → P4CSSEALED
Authorization candidate passed 34/34 tests and was sealed.
- P4D → P4DSSEALED
Data/migration contract candidate passed and was sealed.
- P4E_R4 → P4ESSEALED
PostgreSQL 18 tenancy/governance candidate passed 27/27 assertions and was sealed.
- P4FSAFE STOP
Runtime authorization candidate was not accepted. The stop is preserved as evidence.
- P4F_R2PARKED
Runner/package remains parked and explicitly unauthorized.
- Source-28 installPASS
R5 installed the exact 28-source governance canon plus master handoff without runtime, DB, provider, Git-history or parked-P4F mutation.
- Source-28 sealSEALED
29 governance paths committed and tagged; parked P4F hashes remained unchanged.
- Pause boundaryFROZEN
PRAXIS intentionally paused here for a temporary public status-page side quest.
The problems we hit — and what they hardened
The Source-28 side quest exposed multiple PowerShell/harness failure modes. None were allowed to silently become product authority.
| Attempt | Result | Problem | Containment | Correction |
|---|---|---|---|---|
| Initial Source-28 installer | STOP | Call-depth overflow after package-manifest validation. | No acceptance claimed; installer abandoned. | Rebuilt as a standalone non-recursive runner. |
| Source-28 R3 | STOP | PowerShell 5.1 StrictMode exposed scalar .Count behavior. | Failure occurred before documentation install/write stage. | Replaced scalar-sensitive count checks with PowerShell-5.1-safe enumeration. |
| Source-28 R4 → R5 | RECOVERY | Evidence location was too buried for the operating workflow. | No authority change; evidence workflow corrected. | R5 emitted PASS/STOP evidence directly into Windows Downloads and then passed. |
| Source-28 seal R1 | STOP | PowerShell parser rejected variable interpolation followed by a colon: $hookCode: / $newHead:. | Script never parsed, so no Git mutation executed. | Delimited variables and added parser preflight. |
| Source-28 seal R2 | STOP | A helper parameter named $Args collided with PowerShell's automatic $args variable, causing a bare git invocation. | Stopped at first Git state read; no commit or tag created. | Rebuilt the Git helper and added argument-forwarding self-test. |
| Source-28 seal R3 | PASS | None remaining at gate execution. | Exact governance-only stage set enforced. | 29 governance paths sealed; parked P4F preserved byte-for-byte. |
Parked means preserve
These four known P4F candidate paths are intentionally dirty/parked. Dirty does not mean wrong. They must not be reset, cleaned, overwritten, staged or promoted by accident.
- apps/api/package.json
- apps/api/src/authorization-repository.ts
- apps/api/src/authorization-runtime.ts
- apps/api/test/authorization-context.test.ts
Side quests that protected the mainline
These were not random detours. Each one reduced ambiguity, hardened evidence handling, or protected the sealed boundary.
Runner hardening
COMPLETE
Converted repeated PowerShell/harness failures into parser preflight, argument-forwarding tests, fail-closed evidence and exact mutation boundaries.
Evidence ergonomics
COMPLETE
Changed runners so PASS/STOP evidence lands directly in Downloads for immediate review.
PRAXIS LIVES status page
ACTIVE SIDE QUEST
Temporary public read-only showcase/status surface for the meeting. It does not advance or mutate PRAXIS product authority.
Where the build goes next
The queue is frozen, not abandoned. Exactly one implementation gate is next when PRAXIS resumes.
| Gate | Foundation slice | Status |
|---|---|---|
| P4F | Actor + membership authorization runtime v2 | NEXT / FROZEN |
| P4G | Capability registry + module-manifest foundation | QUEUED |
| P4H | Products, plans, plan versions and entitlements | QUEUED |
| P4I | Usage meters, budgets and credit ledger | QUEUED |
| P4J | PRAXIS SaaS billing adapter — sandbox first | QUEUED |
| P4K | Release fabric, rollout, dependencies and kill switches | QUEUED |
| P4L | Tenant commerce domain contract | QUEUED |
| P4M | Embedded payments / Stripe Connect foundation — sandbox | QUEUED |
| P4N | Agent identity, delegation and risk | QUEUED |
| P4O | Transactional outbox + durable execution | QUEUED |
| P4P | Memory/cache foundation | QUEUED |
| P4Q | Public API/webhook/service-account/MCP seam | QUEUED |
| P4R | Cross-layer integration/torture/security gate | QUEUED |
| P4S | Commercial platform foundation seal | QUEUED |
First sellable CRM sequence
- Contacts + companies / account 360
- Leads, deals and pipelines
- Tasks, activities and universal timeline
- Operational inbox
- Email/SMS integrations
- Quotes, invoices and payment links
- Simple workflows
- Agent CRM assistant with credits and approval
- Public API and webhooks
- Reporting and next-best action
Commercial direction
Serious CRM for small teams, expanded continuously by sealed capabilities.
- Free
- Useful core CRM; limited team/API/webhook/AI/automation as those capabilities are released.
- Team
- More users plus practical integrations and higher automation/API capacity.
- Pro
- Advanced automation, custom roles/objects, more agent/usage capacity and advanced reporting.
- Business
- Larger teams, governance, retention/admin/security-management features and higher capacity.
Not sealed yet
- Exact production prices
- Exact user/seat counts
- Exact included credits/allowances
- Production billing activation
Safety, quality and truth rules
The status page does not inflate claims. It reflects the same default-deny, evidence-first posture as the product.
- Security
- Tenant isolation, safe authentication, default-deny authorization and basic audit are universal product requirements.
- Evidence
- Candidate is not authority. STOPs remain visible. Seals must tie exact hashes/paths/tests to an accepted boundary.
- Accessibility
- WCAG 2.2 AA is the engineering/design target, not an automatic conformance claim.
- Compliance claims
- No unsupported SOC 2, HIPAA, GDPR, WCAG or 'bank-level' claims.
- Payments
- Tenant commerce and PRAXIS SaaS billing remain separate domains; live provider mutation requires explicit authorization.
- Agents
- No raw database authority, no implicit money authority, and no prompt-based bypass of authorization.
Resume protocol
When the side quest ends, PRAXIS returns here. No drift, no stale runner, no accidental cleanup.
- Confirm current Git authority still matches praxis-src28-v1 / 8b984b3638a134cbce9a0c8fa965fb2c4ab576ac or identify newer accepted evidence.
- Read PROJECT_SOURCE/00_READ_FIRST.md, 01_CURRENT_AUTHORITY.md, 02_MASTER_SOURCE_OF_TRUTH.md, 03_PRODUCT_CONSTITUTION.md and 04_ARCHITECTURE_CONSTITUTION.md before architecture work.
- Read 07_IDENTITY_TENANCY_AUTHORIZATION.md and the roadmap/ledger before touching authorization runtime.
- Preserve the four parked P4F paths; do not reset/clean them merely because the worktree is dirty.
- Do not run old P4F_R2.
- Start with a newly reconciled P4F v2 contract/candidate under the Source-28 control chain.
- Require evidence before acceptance/seal; do not invent a remote or mutate production/providers without an explicit gate.
This is a static public snapshot of the latest verified PRAXIS evidence, not a direct connection to the private repository or production systems.
Viewer clock: