Skip to content

[Dijkstra] Computational instances for remaining rules #1071

@williamdemeo

Description

@williamdemeo

Description

We probably don't need new Computational instances for the rules that are imported or copied over from Conway, but we should confirm this.

Check whether the following rules need new Computational instances: BBODY, ENACT, EPOCH, POOLREAP, RATIFY and RUPD rules.

The goal is to provide an executable interpreter for the rules within the Dijkstra batch/nested transaction context (CIP-118).

Scope of Work

  • Import, copy, or implement new Computational-BBODY for _⊢_⇀⦇_,BBODY⦈_ relation.
  • Import, copy, or implement new Computational-ENACT for _⊢_⇀⦇_,ENACT⦈_ relation.
  • Import, copy, or implement new Computational-EPOCH for _⊢_⇀⦇_,EPOCH⦈_ relation.
  • Import, copy, or implement new Computational-POOLREAP for _⊢_⇀⦇_,POOLREAP⦈_ relation.
  • Import, copy, or implement new Computational-RATIFY for _⊢_⇀⦇_,RATIFY⦈_ relation.
  • Import, copy, or implement new Computational-RUPD for _⊢_⇀⦇_,RUPD⦈_ relation.
  • Import, copy, or implement new Computational-SNAP for _⊢_⇀⦇_,SNAP⦈_ relation.
  • Import, copy, or implement new Computational-TICK for _⊢_⇀⦇_,TICK⦈_ relation.

Metadata

Metadata

Assignees

Type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions