- Shell 68.1%
- Forth 18.2%
- Python 13.7%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| facts | ||
| groups | ||
| reports | ||
| state | ||
| .bash_history | ||
| .gitignore | ||
| all-reports.md | ||
| classify_before_interpret.py | ||
| concat-repo-reports.sh | ||
| existence.fs | ||
| file-list.txt | ||
| ideal-embodied-paradigm-loop-closure.md | ||
| publish-github.sh | ||
| README.md | ||
| repo-report.sh | ||
| summarize-repo-reports.sh | ||
| summary.md | ||
| workspace-report.md | ||
repo-reports
Repository-level reports for a larger research workspace.
This repository collects structured observations and analyses of repositories in the workspace. The goal is to make relationships across projects easier to inspect without treating the current state of any single repository as the whole history.
Structure
facts/
reports/
summary.md
workspace-report.md
facts/— Extracted information about each repository, kept close to observable repository state.reports/— Repository-level analyses derived from those facts.summary.md— A compressed view across individual reports.workspace-report.md— Examines the workspace as a whole, including recurring concepts, related projects, differences between implementations, and possible lines of development across repositories.
The separation between facts and reports is deliberate:
repository
facts/<repository>.txt
reports/<repository>.md
summary.md
workspace-report.md
This preserves intermediate evidence rather than retaining only the final interpretation.
What is being examined
The workspace includes theoretical writing, computational experiments, implementations, utilities, older versions, backups, and projects applying related ideas in different domains.
Recurring subjects include:
- Admissibility
- Persistence
- Continuation
- Constraint
- Reachability
- Repair
- Irreversibility
- Representation
- Memory
- Entropy
- Computation
- Complex systems
The reports help determine:
- Where repositories share an underlying structure
- Where terminology has changed
- Where one project develops or tests another
- Where apparent similarities are only superficial
Older and parallel repositories remain part of the analysis because differences between versions can be informative. A superseded implementation or abandoned formulation may still provide evidence about how a concept developed.
Scripts
| Script | Purpose |
|---|---|
repo-report.sh |
Generates repository-level material |
concat-repo-reports.sh |
Combines individual repository reports |
summarize-repo-reports.sh |
Produces a higher-level summary across reports |
publish-github.sh |
Supports publication of generated material |
Generated files are kept alongside the scripts so that the analysis itself can be inspected and revised.
Levels of analysis
The workspace can be examined at several scales:
file
|
v
repository
|
v
repository group
|
v
workspace
Git history describes changes within repositories. Repository reports describe their contents and relationships. Other historical traces, including shell activity where available, can provide additional evidence about how work moved between projects.
Scope
This repository is not intended to establish a single canonical interpretation of every project. Reports are analytical artifacts and should remain distinguishable from the facts from which they were produced.
The longer-term aim is to make the development of the workspace inspectable as a connected research history rather than as a collection of isolated repository snapshots.
Generated reports are analytical artifacts — interpret with context.