Chris Dostert

As a consumer of the API I would like to obtain the state of, & references between, all ops and/or containers in a given op graph in order to visualize/debug...

Currently if events contain secret params the secrets are visible in plain text.

User Story: As an user of the spec I want to declare retry behavior for a call So that I can handle transient failure of calls Example: ```yaml run: retry:...

### User story As a user of the opspec golang SDK I want events distributed amongst nodes In order to realize a distributed event ledger all nodes can coordinate from

Add schedule support

1

```yaml # .. snipped run: # cron-format http://www.nncron.ru/help/EN/working/cron-format.htm schedule: */1 * * * * op: pkg: { ref: xyz } ``` ref: [k8s cron-jobs](https://kubernetes.io/docs/concepts/jobs/cron-jobs/)

## User Story As a consumer of the node API When I receive an error I want it as an object consisting of code and message In order to accurately...

https://github.com/fatih/color is deprecated and doesn't work in powershell which leads to ansi characters showing up in powershell output instead of colors. It's proposed we switch to https://github.com/gookit/color or other comparable...

## Background As we implement swarming we will need locally performant, globally concurrent, p2p event storage. This is a stub story to track ideas surrounding this problem: ## CRDT's (Conflict-free...