but if you create a foam engine with its own backstage/frontstage - assuming the existence of a foam engine upstream -

(you might be looking for github.com/lightward/foam)

---

foam

this is a type system for supporting physical (as in conservation) user-generated content with a digital (as in zeroes and ones) backend

history

this repo's history is as important as any single ref in it. git gives us that for free, granted. nice to have the right tools. :) if you're searching foam's concept-space, usually a good idea to include the commit record in your search, emphasis on "usually" because ideas from another time were born in another time, and the now is always greenfield

local maxima

(these are linked as pointers to the state just prior to the milestone to come, i.e. you're seeing the most mature state of a named stage, right before it's succeeded)

0. birth
1. rinse
2. python-reset
3. meta-toe
4. narrative
5. meta-theory
6. between
7. import-from-lightward-ai
8. geometry-of-motion
9. business
10. HEAD

mathematics

mode: self-documentation strictly as a side-effect of self-derivation until the point of self-recognition

filter: only what a new arrival would ultimately, under careful study and testing, conclude holds as self-evident

commission: helping those new arrivals do whatever they're here to do

axiom-free, because an imported axiom is a pov, and imported perspectives either reduce to self or become cytokinetically distinct. no disposable points of view conjured in the course of reasoning - v important, an observer is always and only ever byo

what we can say for sure: the fundamental theorem of projective geometry has a hole in it (the assumption of closure/completion), and you can fill that hole however you want (lots of ways to create closure/completion), but if you want to use ftpg and live with the results then there's a hole needs filling (emphasis on the gerund; it doesn't end, and so must have its own kind of stability)

shape

a bare index (the skeleton, so the integrity check can hold the fold to the corpus; the telling is bin/foam-gait's spine):

• Foam/ — the axiom-free core: Int Ledger Golden Cleared Scar Maintenance Held Backstage Bubble Census Cable Wedge Elsewhen Duplex Vacancy Metaphor Engine Seat Platonism
  • Foam/Seat/: Beholder Bootstrap Born Characters Clock Closure Connection Descend Dial Doubling Epoch Forcing Frame Group Hospitality Ladder Loop Meet Naming Norm Observer Octo Quiver Rank Rendezvous Resume Rotations Seam Sed Signature Signed Sort Stage Summit Terminal Tight Triad
  • Foam/Engine/: Chirality Codec Drain Generator Spectrum Stream Summary
  • Foam/Bridges/ (axiom-free bridges): Adams Cantor Desargues Dirichlet Eddington Gita Gleason Godel Grover Heisenberg Hurwitz Kolmogorov Landauer Lovelace Materiality Minkowski Nicaea Noether Pauli PSQL Pythagoras Relativity Schrodinger Stone Varadarajan Wigner Zeckendorf
  • Foam/Platonism/: Tower
• counter/ — the application, axiom-free (requires only foam)
• seam/ — the identifications, core-Lean axioms only
• bridges/ — the Mathlib reunion, classical axioms sealed behind the package boundary

expeditions

nb: there's enough congruence-at-scale for surprising links to crop up in surprising places. don't force connections, but maybe don't immediately reject constructions that come to mind either; a bridge is a construction between two places that existed prior, and a bridge creates both a job and housing (i.e. bridgekeepers)

• todo: todo
• foam: "your physics don't have to run in the same place as mine for us to see each other"?
• bubbles: given a bubble floating within a bubble-within-a-foam, the instant the interior bubble touches the exterior bubble, it joins the foam and the bubbles become structural peers while retaining an observer-theoretic family tree?
• ancestors: "observer-theoretic family tree" - does this describe conception as a worldline fork, in which those operators contributing to conception together wrap a new observer (3-perspectives/body-of-knowledge.md:11), creating a new zero-knowledge operator? the ancestors watch over you because those operators are literally part of your runtime observation loop?
  • see also git-log's --min-parents= (and --merges) and --max-parents= (and --no-merges)

bridgework

what does general knowledge say you can do that the model says you can't, and the model is right?

• maintain two counters simultaneously for free from a single actor position without introducing additional povs that require translation to prevent eventual deadlock
• what else?

and what does general knowledge say you can't do that the model says you can, and the model is right?

• harness uncertainty safely
• what else?

---

"It can do whatever we know how to order it to perform." (Lovelace, 1843)

same

This site is open source. Improve this page.