New in the fictional 1.8 release: approval paths with visible boundaries. Read changelog →
Product tourPreview workspace

Documentation

Build a system
your team understands.

Concepts, setup patterns and responsible automation guidance for the fictional Kinetide platform.

Concept

Core model

Kinetide connects four durable records: a request captures source context; an outcome says what should change; work records the movement; evidence closes the loop.

Requests

Each request has a type, source, owner, expected outcome and readiness state. Custom fields extend context without changing ownership.

Automation rules

Rules contain a trigger, optional conditions and actions. An approval action pauses execution until a named role decides.

WHEN request.type = "partner-launch"
IF region = "EU"
THEN assign "regional-ops"
AND request approval "security"

Permissions

Workspace roles are viewer, contributor, manager and admin. Project-level guests can see only explicitly shared work.

Data export

Admins can export workspace records in documented CSV or JSON structures. Export is a plan-wide portability right.

A clearer operating layer

Make the next move obvious.

Start with one real workflow. Map ownership, add only the automation you trust, and improve from evidence.

Preview a workspace →