A library for communication between Languages. The indexing, analysis ..., comparison of existing abstract models of computation, mathematics, calculi, theorem-provers, compilers, proof assistants, automated program synthesizers, ..., (programming) languages.
- Prerequisite: [[Writing - 2025. A Universal Language]]
- Collaboration Setup
- Collaboration tooling: Create a way of analyzing/comparing them which does not include manual human labor of specifying their grammars.
- Compile scripts for this repository, so a writing/study of this can be automatically compiled to some PDF, ..., LaTeX setting.
- [[People Index]]
- Compile a list of people who need to be contacted for this
- [[Finding Collaborators]]: Are there people who have compiled something like this yet? There are probably many people who are thinking about something like this in the context of biology, meta-research, ..., other fields too. Find out who?
- [[Legal]]: Just exclude the ones without open licenses or contact all of them to lift the licenses.
- [[Project Index]]
- Expand
- Version Control
- Game-side (& merge from [[Project - Research towards Designs (2024-2025)#Research of Games, Engines, ...]])
- [ ]
- The only stuff I've been able to find so far is either incredibly limited in scope or is doing too much of this by hand. Would love to find out that there's someone who has been working on this already though.
- Differentiation: Measurement of category if diversity for the thing its useful for ; this is essentially the closeness idea (More usefully: How much do I need to change/ignore before they're the same to me?)
- Basically, how much shifting/.../ignoring do I have to do before particular kind of symmetries/equivalences are reached so there's an/.../better interface into it.
- Becomes "contextual/.../computational closeness?"
- Storage/Structure/orbits as compute
- How to phrase storage as compute? It's using some compute to persist some structure, though we might not know how to use it for anything else than storage, this is essentially the case. All equated as the same resource? Persistence/Compute/Effort/resources
- Structure vs combinators from certain perspectives that sort of thing?..., energy, conservation
- at the end simple example of efficiency/closeness/differentiability
- Language barriers / Different perspectives
- Get things like taking items from one particular world back to another world, could suddenly see quests you couldn't see before (immigration / ...).
- Switching between different abstraction levels
- What are mistakes in trying to spin up new projects/languages?
- Compiled grammar vs analysis of runtimes?
- What can be (partially) compiled to what using what? (Natively supported vs finding (accidental) symmetries to allow for compilation)
- Apply this question again by loosely changing constraints?
- noticing of runtime inconsistencies from some perspective ; adjustable
- What mistake in indexing multiple levels of descriptions ; Non-overlap, points resulting in confusion etc..
- Realized invariances/.../redundancies of particular layers.
- Part of this becomes how do certain fields/perspectives/projects have a view on other projects (partly [[PENDING (2032+?); Sociology, Economics]]). A simple example is confusion between programming fields in what the meaning of frontend/backend is. - People's fixation on using a particular word very specifically. That sort of thing.
- complex/complicated is another example
- another is hardware/software distinction (in the sense of superposed languages, this fails a bit). This distinction isn't really that clear-cut.
- Expand