Edition README
Stratified Relational Workspace Theory
README.md
1 # Stratified Relational Workspace Theory
2
3 **A Core-Transfer Framework for Distributed Cognition, Collaboration, and Epistemic Systems**
4
5 - **Author:** Komorebi P.
6 - **Repository version:** `1.0.0`
7 - **Status:** Complete preprint monograph; external mathematical and empirical review pending
8
9 [Read the 209-page monograph](monograph/Stratified_Relational_Workspace_Theory.pdf)
10
11 ## Overview
12
13 Stratified Relational Workspace Theory studies when a collection of people, models, artifacts, instruments, and computational processes supports a genuine shared workspace rather than replicated storage, centralized control, or merely correlated activity.
14
15 A stratified relational workspace is defined as a temporally persistent, causally efficacious, jointly reconstructible structure represented only partially in several heterogeneous components. Its identity is determined by invariants preserved under admissible transfer, and its operative capacity is relational only when no individual component or matched local-storage null reproduces the relevant function.
16
17 The central identity principle is
18
19 $$
20 \boxed{\text{workspace identity}=\text{persistent invariant causal organization under admissible transport}.}
21 $$
22
23 The framework does **not** infer consciousness, personhood, moral status, or unrestricted autonomy from structural coherence, agency, or self-maintenance.
24
25 ## Scope of the monograph
26
27 The theory develops five connected layers:
28
29 1. **Structural geometry.** Heterogeneous local state spaces, core-residual decompositions, compatible global sections, holonomy-fixed cores, transfer Laplacians, spectral stability, gauge covariance, and pathwise leakage.
30 2. **Operational relationality.** Canonical predictive states, feasible interventions, coalition risk, matched relational nulls, causal specificity, and reentry.
31 3. **Persistence and identity.** Moving workspace subspaces, reconstruction frames, erasure resilience, handoff, replacement invariance, gluing, and hierarchical composition.
32 4. **Formation and agency.** Learned transfers, boundary recovery, provenance, goal retention, counterfactual policy evaluation, damage detection, repair, and self-maintenance.
33 5. **Epistemic robustness.** Faithful coarse-graining, decomposition robustness, specification robustness, experimental identifiability, partial identification, and uniform finite-sample certification.
34
35 The individual mathematical ingredients are largely established. The candidate contribution is their noncompensatory integration into one falsifiable certification architecture, together with matched near-miss systems that the certificate is designed to reject.
36
37 ## Repository structure
38
39 | Path | Purpose |
40 |---|---|
41 | [`monograph/`](monograph/) | Canonical modular LaTeX source and compiled PDF |
42 | [`archive/v1.0.0/`](archive/v1.0.0/) | Frozen single-file source snapshot from which the modular source is generated |
43 | [`verification/`](verification/) | Deterministic mathematical regression checks and reference outputs |
44 | [`audits/`](audits/) | Priority register, theorem-like statement index, and verification records |
45 | [`docs/`](docs/) | Build, review, reproducibility, licensing, release, and publication guidance |
46 | [`scripts/`](scripts/) | Cross-platform build, verification, packaging, and source-splitting utilities |
47 | [`.github/`](.github/) | Continuous integration, tagged-release automation, issue forms, and pull-request templates |
48
49 ## Build
50
51 A recent TeX Live installation with `latexmk` is required. From the repository root:
52
53 ```bash
54 python scripts/repo.py build
55 ```
56
57 Equivalent Make target:
58
59 ```bash
60 make build
61 ```
62
63 Windows PowerShell:
64
65 ```powershell
66 python .\scripts\repo.py build
67 ```
68
69 The generated PDF is written to `build/Stratified_Relational_Workspace_Theory.pdf`.
70
71 Detailed platform notes are in [`docs/BUILDING.md`](docs/BUILDING.md).
72
73 ## Verify
74
75 Install the Python verification dependencies:
76
77 ```bash
78 python -m pip install --requirement requirements.txt
79 ```
80
81 Run the complete repository audit:
82
83 ```bash
84 python scripts/repo.py verify --strict
85 ```
86
87 Strict verification checks:
88
89 - successful LaTeX convergence;
90 - absence of unresolved references, duplicate labels, box warnings, and LaTeX warnings;
91 - the expected 209-page output;
92 - embedded fonts and unencrypted, text-based PDF output;
93 - extracted-text equivalence between the rebuilt and committed PDFs;
94 - exact correspondence between the modular source and frozen monolithic snapshot;
95 - repository metadata and internal Markdown links;
96 - all deterministic mathematical regression checks.
97
98 See [`docs/REPRODUCIBILITY.md`](docs/REPRODUCIBILITY.md) for the verification model and its limits.
99
100 ## Package a release
101
102 ```bash
103 python scripts/repo.py package --strict
104 ```
105
106 This produces a versioned PDF, source ZIP, source tarball, and `SHA256SUMS.txt` under `dist/`. Pushing a tag such as `v1.0.0` activates the included release workflow.
107
108 ## Review and contribution
109
110 The preferred review path is issue-first. Mathematical reports should identify the statement label, assumptions, precise concern, and either a counterexample, proof gap, or proposed correction. See [`CONTRIBUTING.md`](CONTRIBUTING.md) and the [`review guide`](docs/REVIEW_GUIDE.md).
111
112 The [`statement index`](audits/statement_index.md) lists every theorem, proposition, lemma, corollary, definition, example, and remark. The [`priority register`](audits/priority_register.csv) distinguishes standard machinery, adaptations, synthesis claims, and unresolved empirical claims.
113 The [`GitHub readiness report`](audits/github_readiness_report.md) records the clean-checkout, packaging, Git, and PDF-regression audit.
114
115 ## Citation
116
117 Citation metadata is available in [`CITATION.cff`](CITATION.cff) and [`CITATION.bib`](CITATION.bib).
118
119 ## License status
120
121 This release is publicly readable but is currently **not distributed under an open reuse license**. All rights are reserved unless applicable law or separate permission allows reuse. The rationale and possible future licensing options are documented in [`docs/LICENSING.md`](docs/LICENSING.md).