This page helps us have a clear vision of all necessary processes and permissions the system requires.

Data Actions

• Get Record & Get Index
• Push Primitive
• Set Taxonomies

Stream Actions

• Create Primitive Stream
• Create Composed Stream
• Disable stream
• Transfer ownership

System Actions

• Create contract
• Drop contract
• Transfer contract ownership

Data Permissions

• Allow read (by wallet)
• Allow push primitive (by wallet)
• Allow update taxonomy (owner only)
• Allow inclusion in taxonomy (by stream id)

Stream Permissions

• Allow create stream (by wallet)
• Allow disable stream (owner only)

System Permissions

• Allow create contract
• Allow drop contract (owner only)

Processes Exploration

Creating Streams

Pushing primitives

Updating Taxonomies

Transferring ownership of Stream

Requesting Stream Officialization

Reading System Streams

Reading 3rd Party Streams

Favorite Processes Description

However, you may find other alternatives on each process exploration page. All favorite processes should be compatible with the favorite architecture.

Creating Streams

1:1 Contract:Stream

Each stream is a contract. Based on contract decentralization, third-party streams are enabled and encouraged to achieve a constrained evolution.

Note: we didn’t define how to gate contract deployment. Should this gating mechanism be kwil built in?

Pushing primitives

Dynamic Metadata Version

Authorization metadata and logic reside in the Stream Contract. In this way, 3rd party streams can already apply permissioned access to data.

Updating Taxonomies

Taxonomy updates should be more restrictive than pushing primitives. Owner-only should suffice.

Requesting Stream Officialization

Information is stored in system_streams table inside the System Contract. Ownership is transferred to the TSN wallet. Checks need to occur, initially manually.