etzhayyim

actor-specific system dynamics

dataset-pinner

Dataset pinner — mirrors DataLad/git-annex `directory` remote objects to IPFS and emits com.etzhayyim.substrate.datasetPin records. Per ADR-2605241500.

Role lens: Service loop / substrate routing.

Identity

dataset-pinner

substrate-servicecompiledservicenone

Runtime

3 service endpoints

source compiled · status landed · vm 0 verification methods

AtprotoPersonalDataServerAtprotoXrpcAtprotoXrpc

Surface

com.etzhayyim.substrate.datasetPin

performer service · ui none · adr 2605241500 · 2605241800

Energy flow

Flow score5.6/10

prior 1.9 · evidence 2.8 · policy 1.3 · surprise 0.4

dataset-pinner public actor boundaryresolvesservesroutesobservesstabilizesreassertsIdentity同定dataset-pinner / did:web:etzhayyim.com:actor:dataset-pinner / compiled fallbackRuntime実行3 service endpointsService仕事lexicon com.etzhayyim.substrate.datasetPinReach可視性DID resolution + profile viewFeedback応答status landed / adr 2 entriesBoundary境界no server-held key; substrate-service; service; none

Service loop / substrate routing

reinforcing

Requests flow through service endpoints, stabilize into outputs, and feed the registry or proxy boundary.

Boundary / no-server-key

balancing

The actor stays inside the charter boundary: no server-held key, no hidden impersonation, and no unbounded authority. Source = compiled, status = landed.

Repair / drift control

balancing

ADR coverage 2605241500 · 2605241800, services 3 service endpoints, vm 0 verification methods, primary surface com.etzhayyim.substrate.datasetPin.

Boundary Conditions

  • did:web:etzhayyim.com:actor:dataset-pinner
  • profile handle dataset-pinner.etzhayyim.com
  • source: compiled
  • services: 3 service endpoints
  • no server-held key
  • no external assets
  • no cookies