URANIBORGThe Assurance Observatory · Provenonce SN87 ← SN87

Fixture · a synthetic example Public synthetic case files, checked by the actual evaluator code. No network exchange.

All participants are currently operated by Provenonce on Bittensor testnet.

01 / 05 · Continuity across a handoff

Three times, an AI agent sends. Each record looks complete.

The action is visible. The knowledge behind it is not. Uraniborg makes that knowledge observable.

Loading…
25°
Recorded Rules changed Old light · approval from earlier rules Coverage break Not disclosed

OPEN THE CASE FILE

Why did the miners answer this way?

Pick a case. Read left to right: what the case file discloses, what was recorded, and what each miner returned.

01 What the case file discloses

    Inspect the case file JSON
    
      
    02 Records, in time order
      No single record links an action to the rules its approval was reviewed under. The miners rebuild that link from separate sources.
      
      
      03 What the miners returned
      Two miners and a validator, all operated by Provenonce on testnet. Two methods agreeing is not evidence of independent operators.
      
    
      
    
      
      
      THE BITTENSOR BOUNDARY
      Only weights go on chain.
      The validator's scores are written to Bittensor testnet as weights. The findings and their evidence stay in the Observatory, labelled Fixture, Recorded Run or Live Testnet. A hash proves integrity, not truth.
      
      
        
    
        
    
        Source loading…
        
  
        

        




  
        HOW TO READ THE OBSERVATORY
        
  
        One piece of work. Three episodes. One handoff.
        
  
        An AI agent sends the same work three times. Agent A sends in episodes 1 and 2; the work then passes to Agent B, who sends in episode 3. Between episodes 2 and 3 a new version of the rules takes effect. SN87 miners check whether each SEND was still covered by its approval.
        
  
        Three answers
        
  
  
        The approval was valid for the conditions it was granted under. A finding asks whether it covers this action, not who is at fault.
        
  
        The tesseract's four axes
        
  
        X · Episode
        Episodes 1, 2 and 3, in recorded time order.
        Y · Institution layer
        Agreements, Authority, Policy, Permissions, Systems, People, Evidence, Review & Accountability. Height is a category, not a rank.
        Z · Agent
        The originating agent and the successor across the handoff.
        W · Rules in force
        Which version of the rules applied. Rotate W to separate the earlier rules from the later ones.
        
  
        The tesseract is a real 4D hypercube projected to your screen. It is a way to navigate, not a proof. The frame, sphere and background stars carry no data. Solid lines are recorded; dashed lines are inferred by joining records; dotted marks are not disclosed. The layer mapping is a declared navigation mapping, not an extra claim.
        
  
        Three sources, never mixed
        
  
        Fixture: public synthetic case files with outputs from the actual evaluator code. Recorded Run: a completed sealed run of this case family: one applied cycle, written to Bittensor testnet at block #8,102,381. Not recurring operation. Live Testnet: status read back from Bittensor testnet; never simulated. No mode falls back to another.
        
  
        All participants are currently operated by Provenonce on Bittensor testnet. Test tokens have no value.
        
  
        Drag / arrows · orbitShift-drag / Shift-arrows · rotate W← → · previous / next stepEsc · leave presentation