Appearance
Liberty by Design — SocioProphet
This document is intentionally product-scoped. It defines the constitutional commitments that should govern SocioProphet as a knowledge, governance, education, and evidence system for people and institutions.
Cross-repo workspace doctrine, OS/runtime substrate doctrine, and agent-plane orchestration doctrine should live outside this repo, primarily in SocioProphet/sociosphere.
1) The product problem: epistemic capture inside institutional systems
Most institutional software does not fail because it lacks data. It fails because it turns data into a bottleneck, hides reasoning, obscures provenance, and makes challenge expensive.
A product becomes dangerous when it silently converts:
- evidence into authority theater
- dashboards into unquestionable truth
- governance into invisible enforcement
- AI assistance into unappealable output
SocioProphet should resist that shape.
The product thesis is simple: understanding must remain distributed, challengeable, and replayable.
2) Evidence before authority
SocioProphet should not ask users to trust claims because a prestigious actor, internal workflow, or model produced them. It should structure claims so they can be inspected, challenged, and replayed.
That means product surfaces should favor:
- provenance over assertion
- evidence pointers over summary theater
- traceable diffs over silent mutation
- replayable workflows over black-box outcomes
The enemy is not disagreement. The enemy is non-inspectable power.
3) Privacy for persons, transparency for power
This repo’s product doctrine should preserve a hard asymmetry:
- persons deserve privacy
- power deserves transparency
In product terms, that means:
- intentional publication boundaries
- audited access to sensitive material
- selective disclosure when possible
- visible policy for restricted operations
- durable traces for consequential institutional decisions
If the product flips this asymmetry, it becomes a surveillance instrument wearing a governance costume. That costume is clown shoes with a security badge.
4) Education as a first-class product function
SocioProphet should not merely deliver conclusions. It should improve the user’s ability to inspect, interpret, and challenge those conclusions.
Product features should therefore support:
- explanation
- replay
- comparison
- correction
- curricular propagation
- institutional memory
A healthy product increases human capability per unit of machine assistance. A bad product increases dependency per unit of machine assistance.
5) Accountable machine assistance
Machine assistance is allowed inside this doctrine only when it remains bounded, attributable, and reviewable.
In product scope, this means:
- AI outputs should carry evidence context where possible
- consequential actions should expose inputs, constraints, and policy context
- denials should be explainable and appealable
- moderation/governance actions should leave structured traces
- replay should be available for critical workflows
The product may assist judgment. It must not counterfeit legitimacy.
6) Governance must be visible and appealable
Invisible enforcement is the authoritarian bug pattern of software.
SocioProphet product surfaces should therefore make governance legible:
- what rule applied
- what evidence was used
- what action occurred
- what changed
- how to appeal or challenge
Default-deny is acceptable when paired with visible reasons, evidence pointers, and a structured appeal path. Silence plus coercion is not governance. It is productized priestcraft.
7) Product invariants
The following invariants should be treated as acceptance criteria for SocioProphet product surfaces:
- No consequential action without evidence.
- No durable claim without provenance.
- No governance action without visibility.
- No denial without an appeal path.
- No replayable-critical workflow without a replay recipe or equivalent audit surface.
- No publication of personal material without explicit policy basis.
- No silent mutation of institutional truth.
- No AI summary that cannot be challenged against underlying evidence.
If these invariants fail, liberty becomes branding copy instead of system behavior.
8) What belongs elsewhere
This repo is not the right home for every neighboring doctrine. The following topics should primarily live in SocioProphet/sociosphere or another infra/workspace repo when they are cross-repo rather than product-specific:
- workspace controller doctrine
- OS/runtime substrate doctrine
- agent-plane orchestration doctrine
- repo composition / materialization doctrine
- transport/wire/runtime capability doctrine when not directly product-facing
That boundary matters because repo ontology is part of governance. If everything lives everywhere, nothing is actually governed.
Related Specs (stubs → formal specs)
These are the implementable surfaces that this product doctrine should map into.
- Rights of Verification Charter v1: spec/constitutional/rights-of-verification-charter-v1.md
- Attestation Envelope v1: spec/security/attestation-envelope-v1.md
- Transparency Log v1: spec/security/transparency-log-v1.md
- Witness Diversity Policy v1: spec/security/witness-diversity-policy-v1.md
- Audit Bundle + Replay Recipe v1: spec/security/audit-bundle-and-replay-v1.md
- Governance Lifecycle v1: spec/governance/governance-lifecycle-v1.md
- Curvature Proxy Metrics v1: spec/metrics/curvature-proxy-metrics-v1.md
- Privacy Boundaries v1: spec/privacy/privacy-boundaries-v1.md
Backlog (next formalization targets)
- Turn the Rights of Verification charter into machine-enforceable product acceptance checks.
- Formalize attestation payloads for claims, datasets, model outputs, and policy decisions.
- Define transparency-log event types for moderation, publication, policy adoption, and institutional review.
- Require replay/audit bundles for critical product workflows.
- Define governance diffs, appeal flows, and reviewer-visible evidence surfaces.
- Operationalize curvature proxies for concentration, suppression, and unverifiable authority.
- Tighten privacy boundaries with selective disclosure and audited restricted access.