Pics Start Date:
Notes Date (end):
CD_024+dump
Deeper details on Scape Specs and Virtual Machine Construction
view (naked) not supported for CD_024+pics
Pics Start Date:
Notes Date (end):
CD_023+dump
*Scape Spec*
(id)
Scape Name
Address Spec: Grammatical structure of key + range constraints?
Keys/Data Sources: Criteria for building collection in scape
Content Spec: Format for the collected content (which may create a new struct from the data sources)
Indexing Functions: For building keys from data + range constraints?
Key Geometry Functions: =, <, >, nearness, next/previous, top/bottom, first/last, range/area, branch/parent/child, comparison/equality, case (sound fingerprint, color, pattern, etc.)
Key Matching Functions: masks, ranges, parsing, lexing, regex, etc.
Data Matching Functions: (for iterative queries) data comparison, regex, *.* masks, parsing/lexing, etc.
Data Geometry Functions: next/prev, first/last, top/bottom, nearness, range/area, branch/parent/child
view (naked) not supported for CD_023+pics
Pics Start Date:
Notes Date (end):
CD_022+dump
Data and scape engine operators.
Data engine creates forms of memory specificed by a "word-spec"
The data engine is the "memory" of the ceptr VM, it's just that there are lots of types of memory, not just RAM accessible by word-sized int. Instead the machine "word" can be semantic structures, stored natively.
Sort/Limit are kinds of meta-geometry functions on scapes
Geometry functions from spreadsheet, (structural and contextual): existance, isometric maps, next/prev, orderded, bounded, linearity, rotational, continuous vs stepped, tree, etc..
Find: search on data that's allready scaped so it can be retrieved via random access
Match: requires iteration and processing.
We took a long walk and explored the issues of "variable equality" in scapes. What it would mean to provide "=" functions that may operate differently at different "resolutions" of scapes. Think of different zoom levels on a map where you'd say two people live in the "same" place at the level of country/bioregion/city/neighborhood/street etc. based on the level of resolution you're working with.
In hindsight, it seems obvious, if scapes are used for fractal sense-making and coherence, that native support different resolutions, as well as different modes of comparison, are necessary.
Also... related to "equality" and "resolution" is the notion as edges as gradients. That boundary patterns may emerge in a post-hoc fashion based on rates of change (density of gradient). There may be ways to detect edges in gradients by watching rate of change of the gradient values.
Emergent low resolution scapes should be able to be built out of high resolution scapes via the expressive capacity, and thus provide "quantum" or highly meaningful resolutions.
Reminder:
- Contextual geometry is to do with relationships within the content of the DATA.
- Structural geometry is to do with relationships within the structure of the KEYS (or indexing functions).
CD_022+keywords
scapes data engine VM
view (naked) not supported for CD_022+pics
Pics Start Date:
Notes Date (end):
CD_021+juicy bits
memory <-> physical machine
data engine <-> virtual machine
sekeletal(structure) and musculature (change) bridged by listening
view (naked) not supported for CD_021+pics
Pics Start Date:
Notes Date (end):
CD_020+dump
Transforms happen at coherence boundaries. This is a reflection of agency being about crossing membranes.
Listening is like event driven models, but there isn't a pre-determined set of events you can listen to rather it's more like stored procetures in a SQL db where you specify what changes in the scape/state/data you want to match on and thus "hear"
What's the equivalent in our virutal machine of the stack frame instructions that are used to impelment calling (and returning from) a procedure in more traditional CPUs.
The possibility of implementing/optimizing scape processing using GPUs, i.e. an element of the scape has a processor assigned to it like a pixel might in a GPU, along with address handling for resolution scaling, etc...
The underlying data engine with smart caching creating true cloud architectures.
CD_020+keywords
SMTP, Log, Logger, Integrate, Integration
view (naked) not supported for CD_020+pics
Pics Start Date:
Notes Date (end):
CD_019+dump
Receptor processing phases/ where
- Hardware/Embodied phase: RECEIVE, verb: receive (native functions: log-write)
- RECOGNIZE, verbs: ack, drop,pass/route,parse (native functions: log-read, log-stats-r/w, pass-in, respond, match)
- Software/Representational phase: REACT/RESPOND, verbs: ignore, integrate, install (native: abstract symbol tree of parsed stream, send signal)
Recognize phase as state machine/truth table of condition, method, log/status
SMTP handler receptor code experiment of above ideas: https://github.com/zippy/ceptr/blob/master/experiments/smtp.clj
Log entry can hold continuity and be a nexus point for interactions of different receptors, i.e. "pulling the string from either direction" The calling and returning from a function can be a result changes in log entry state.
Data Type = carrier + protocol
Carrier: dimension of variability of a substrate
Protocol: method of generating/interpreting variations in that dimension
Scapes: carrier + protocol crossed with carrier + protocol?? Scapes has having matching operations and either having or being optimizations on a carrier
what is the substrate and what is related in that substrate in a scape is an interpretation that can flip, i.e. you can ask for the sound level given a location or vice versa.
CD_019+keywords
carrier protocol scape datatype logging
view (naked) not supported for CD_019+pics
Pics Start Date:
Notes Date (end):
CD_018+dump
Coding experiment of virtual machine as a "stream crosser" i.e. where an stream of instructions is used to interpret a stream of data. Coding experiment at: https://github.com/zippy/ceptr/blob/master/experiments/vp/src/vp/core.clj
Light (transverse waves) propagates using the wave pattern across sub-atomic protocols. Sound (compression waves) propagates using the wave pattern across atomic protocos. Wave partical duality as reading results of a process at different protocol levels. Light pressure (photon as particle) is interpretation at the atomic level. Interference patters is interpreting the results at sub-atomic levels.
- to receive is to log, i.e. a receptor then "has" the sginal
- then we route, transform, etc with a pointer to the log entry which is immutable
- The log is in two parts: 1) the immutable trace/record of signals received, 2) a mutuable control/meta data (accessable via an explicit control channel) about the status of processing that signal. (In the anansi streamscapes implementation this was done as scapes on droplets). I.e. this is a process/status scape on the log.
- The log is kind of like the shared data space we've talked about before, it may be it, or may be stored in it.
The body is the capacity to create juncture between two interpretations of flows. It is cycle, the act of creating an interpretation of one hand as instruction on data on the other hand and then doing that which is meant by that interpretation.
view (naked) not supported for CD_018+pics
Pics Start Date:
Notes Date (end):
CD_017+dump
VM Host Null Protocol (default protocol for bootstrapping or serializing/restarting)
(_NULL_ ENVELOPE:(handlers: (list +(handler-spec:
(map address:int name:string data: (map
code:ceptr-bytecode
aspects: (list *(aspect: (map id:int name:string code:bytecode protocol:grammar)
initialization:bytecode or data? )
) ) )
(bindings: (map *(receptor-aspect:int,int receptor-aspect:int,int) ) )
(manifest: (map *(macro-name:string macro-value:form) ) )
BODY: ( (address:_NULL_ name:"Address-Scape" data:(code:[?????] aspects:[CRUD] init:[hash of key:value pairs])
(address:1 name:"Processing" ...)
(address:2 name:"Memory" ... )
(address:3 name:"FileSystem" ...)
(...)
)
)
These ideas got further developed here: https://github.com/zippy/ceptr/blob/master/examples.proto
namely a notation for the envelope/body nature of the ceptr protocol in the use case of how the virtual machine itself would be described in that protocol.
view (naked) not supported for CD_017+pics
Pics Start Date:
Notes Date (end):
CD_016+dump
[Context: thanksgiving weekend, slowing down, circling around a core]
What is the nature of relationships? The difference between the nature of relationships and the nature of scapes.
In the process of building coherence you establish relationships
hard constraints are embodied in the tools agents use. Soft constraints are represented in the minds of agents
A substrate embodies particular dimensions of variability.
Substrate building feedback loop:
- select/recognize/define a dimension of variability (intent)
- estabish a pattern in that dimension
Possible starting tool for us to build: Coherent Conversationator!
CD_016+juicy bits
Design pattern:
- select/recognize/define a dimension of variability (intent)
- estabish a pattern in that dimension
CD_016+keywords
coherence substrate scape relationship ceptr conversationator
view (naked) not supported for CD_016+pics
Pics Start Date:
Notes Date (end):
CD_015+dump
Last core dump was in June. With the advent of ELL, the space changed so we dropped the practice. However there were some interesting conversations with bits that belong in this series.
- Conversations about agency: Agency is the ability cross a membrane. This way of looking at things explains free-will conundrums, by making agency be something that depends on your view point, i.e. where your awareness is situated in the "membranic whole."
CD_015+juicy bits
- agency is about crossing membranes
view (naked) not supported for CD_015+pics
Pics Start Date:
Notes Date (end):
CD_014+dump
Conversation on Eric's porch
- Emerging Leadership Institute... let's build it and make it go. We could start a small-scale rural one at Sol-Aqua Solar
- Not "distributed database" but "holographic storage model." How exactly would that work?
- Maybe it's not the algebra of scapes that we need but the algebra of relationships... scapes are just the storage format.
- Eric is going to work on Conference Currents with me.
- Conference Currents app could be our first "Releaser" application with a deadline and customer. (SOCAP is Oct 1... needs to be done by Sept 1).
view (naked) not supported for CD_014+pics
Pics Start Date:
Notes Date (end):
CD_013+dump
Currencies at the level of Evolutionary Capacity: Language, DNA, CEPTR, Neurons
view (naked) not supported for CD_013+pics
Pics Start Date:
Notes Date (end):
CD_012+dump
note to self tool (nurture instead of park distractions), reminder, shunter, releaser
ju-jitsu open-the-door to let things through
phone app to record text with a grammar:
transcribe via google-voice on the pbx and send streamscapes
Music as a relational possibility for UI
Relational caledar (i.e. schedule a reminder to core-dump after certain kinds of meeting space).
CD_012+juicy bits
movements/modes in music as a relational tool for natrually revealing kinds of scaped items
CD_012+keywords
scapes, notes-to-self, music, UI
view (naked) not supported for CD_012+pics
Pics Start Date:
Notes Date (end):
CD_011+dump
scape browser/integrator design
serendipty action manager (i.e. non-causal/non-linear project management/to-do list)
Dimensions that contribute to the interface:
We tried out the example of mapping intention space:
- that we organzed according to a plane of interest that cut accross the space (economics), but could have organzed across other spaces
- discovered intention attractors/ intention focusors (example was Land/Labor/Capital) that created a geometry to the "economic" plane.
We re-tried using opportunity:
- created a multi-geometry space that scaped people and organizations with tags some of which were also membranes, and also by ripeness and power/scale.
CD_011+keywords
scape browser, scapes, geometry, mapping, intentions
view (naked) not supported for CD_011+pics
Pics Start Date:
Notes Date (end):
CD_010+dump
Held in the context of Marti Speigleman's Visionary Skills calls.
Worked out basic framework of MetaCurrency call series.
resonance, gifts, membrane. Art coherence holder for first call, perhaps others later
Will serve as curiculum for future web-based offerings.
CD_010+juicy bits
Fed price as a marker of value.
membranes/roles, i.e. coherence-holder
Surface-area for connection
CD_010+keywords
communication, surface area, membranes
view (naked) not supported for CD_010+pics
Pics Start Date:
Notes Date (end):
CD_009+dump
Back to couch-matching example
CD_009+juicy bits
CD_009 Tuesday, May 08, 2012 05:18 PM UTC
view (naked) not supported for CD_009+pics
Pics Start Date:
Notes Date (end):
CD_008+dump
Overall Theme: Understanding the contrast of computing/network architectures of *today* with the architectures of Krafelian Spaces of fractal receptors that we're building (tomorrow).
CD_008+juicy bits
- Messages between nodes on the CEPTR Network are actually just Intra-Membrane messages for CEPTR which can use the data-sync infrastructure because there is only one CEPTR Network Receptor with many instances. It is really just talking to itself.
CD_008+cusp
- The geometry/topology of scapes and their actual implementation
- A full design for the implementation of the CEPTR Network routing system
view (naked) not supported for CD_008+pics
Pics Start Date:
Notes Date (end):
CD_007+dump
- embodied memory ( the informational seed of emerging coherence)
- layer "on top" of this memory producing emergent orders of : identity, again/recurse/loop, resonance w/ core
- eventual emergent orders: extend/reach; informational expansion; gravity; listening to the center/deep memomry; exponentially expanding "surface area"
You write on me, I write on you.
Simultaneous processing listening to other processing creates krafelian space (hands drawing eachother) is fundamentally different from von-Neuman architecture.
Right/Left brain listening to eachother
Our methodology: Pattern of polar overshoot in our inquiry (circling around the pole). Holding existing computing components (git/Turing Machines/programming languages/etc) and waiting to see how they can be used as our frame of reference changes.
CD_007+juicy bits
- first-glue as co-creation of memory (I write on you, you write on me)
CD_007+cusp
- how to use existing tech while holding these ways of thinking in mind, i.e. "wow, I never though git could do that!"
CD_007+keywords
infinity, krafelian space, co-creation, memory, right-brain/left-brain
view (naked) not supported for CD_007+pics
Pics Start Date:
Notes Date (end):
CD_006+dump
"I am" = coherence. It is not only the root process, but the ability for a new aggregation of processes and emergent orders to re-state "I am" is what constitutes a new holonic layer of order... a receptor.
Context: leaving the land, time at the Green River, driving to Williamstown and around Mt. Greylock, walking on the Ashuwillticook rail trail.
Fitness for a purpose. Humanity's fitness for dominion/control: "Mission accomplished" now we are over-fit, time for a new purpose. We need a story of the new creative purpose as well as the Thomas Berry style stories that show our place in an order.
Right relation is renaturalization.
Language is so explicit and have overshadowed process and relationship. In the past right relationship was implicit in culture. Now we have to make it as explicit as language.
Clearing & ritual: balance via rock-stack.
Coherence = energy (in the field of inifinte complexity)
Figure/ground of unity/disunity, identity. falling from complexity to unity AND complexity as unity and creation of identity as disunity.
Potential/kinetic energy in computing systems. Sleep as a potential space. Code as potential energy. Self stored energy as necessary for agency.
Money as stored energy/ fuel for coprporations, viral coherence
Grammar in language as an implicit space for meaning. In general grammars emerge, and create a receptive space for expression. Our work is to create an expressive capacity for creating such grammars. But that meta-grammar will likely not be explicit, rather emergent, a receptive space for the grammars.
Sleep as distributed process synchronization time.
CD_006+juicy bits
- Mission accomplished on control/dominion, consequence of new purpose
- Right relation is renaturalization.
CD_006+keywords
sleep, renaturalization, purpose, grammar
view (naked) not supported for CD_006+pics
Pics Start Date:
Notes Date (end):
CD_005+dump
Started day with a call with JF & Fernanda.
Plant consciousness across all plants (Ayahuasca example)... leading to a deeper discussion of collective consciousness as a kind of morphic resonance for all matched processes. (Of course all Ayahuasca plants share a consciousness because they embody the same process.)
Consider the possibility: since all electrons seem to be identical, maybe there is just one electron. (or at least one electron process with a multitude of extensions into space-time ... like one object class with multiple instantiations).
There is a kind of inversion of "collective intelligence" implied in this. Or rather two distinct layers of "collective" intelligence. One across all humans... another built on the ability for individuated consciousness to speak new coordination protocols "on top" of their individual autonomy. Collective unconscious, meditative states, etc.
And what is the value/richness that this individuated consciousness? New degrees of freedom (think GO... resilience, surface area).
Also... morphogenic fields as a process having emerged which can run _again_.
Our (ir) notation is inherently fractal in its structure... It builds on itself fractally which should yeild natural-like architectures.
A fractal surface presents a consistent interface to any "band" of interaction.
Surface Area Principle: approach the range of variability of the carrier, but don't fill it.
Could we explain the stages of spiral dynamics with our (ir) notation and the orders which emerge that the next layer builds on?
(ir) notation work on fundamental processes:
- me / name / I am / declare
- again / recur
- reach / extension / alloc / dimension
- spin / struct / def
- compare / = / == / bne / subtract=0 / divide=1 / reduce
- expand / multiply / exponentiate / add / unfold / breed
- branch / fork / if then
- ? resonate
- ? mass
- ? friction
- ? moment(um)
- ? bond/connect/relate
- ? cross-breed / combine
- ? breathe
If you use a production grammar the methods of expansion/contraction and their sequence matters a lot for a reliable output.
Our version of a "Turing Machine" would be a surface area, Braunian Space, Krafelian Space, Protocol Space... instead of a machine... it yields a space of possibility for processing.
So... what is the "spin" which turns 1D linear computing to rich multi-dimensional & fractal coherence spaces?
Answer: Circles. Created by a peered address space with agency to declare into that space to hold the center/axis of the spin to allow relating/composing of the computational surfaces.
The network uuid: generated on an axis of agency (one segment as the agent instantiating the receptor into the existence scape / address space of the network) with a timestamp per some shared universal "clock." (pulsar, earth radio, solar something, cesium vibration?)
Phonemes of Agency:
Agent segment as a word composed of parts: ID, SubID, Role...
ID: Type (physical, virtual, legal, communal)
LSD... access to infinite complexity space by suppressing filters
- Right Brain: full spectrum receiver
- Left Brain: tuner/filter/sequencer/constrainer
The magic is in the combining of those two dynamics.
Comparison is contextual. There could be many kinds of comparison... not just our oversimplified notion of equality based on numeracy orientation. e.g. alignment of axes, direction of rotation, radial extension, speed of process, type of process, etc.
CD_005+juicy bits
The whole day was pretty juicy!
- Krafelian Space vs. Turing Machine
- Address spaces to create circles (with agency holding the center)
- Collective Intellegence the layer of morphogenic resonance of like processes
- Phonemes of Agency
- Right/Left Brain dynamics
CD_005+cusp
Global distributed natural clock
Comparison & Context
CD_005+keywords
Krafelian space, collective intelligence, surface area, agency, Turing Machine, spin, fractal computing, (ir) notation, right-brain/left-brain
view (naked) not supported for CD_005+pics