Content Repository
Tools use stable resource IDs instead of unrestricted storage paths.
- Immutable revisions
- Exact relationships between content
- Controlled archiving and deletion
- Content-addressed binary storage
Akyao platform
Tools share a dependable foundation.
Akyao Toolbox connects specialised Windows tools with a shared content repository, clearly defined processing steps and reusable workflows.
System structure
Four responsibilities, one working context.
Each area has a clear purpose. Tools do not need to recreate storage, execution and package management.
- 01
Workbench
Opens multiple tools in a consistent interface with shared interaction patterns.
- 02
Content Repository
Manages resources, immutable revisions, metadata and exact dependencies locally.
- 03
Forge Runtime
Validates and records Functions, converters and flows with typed inputs and outputs.
- 04
Packages
Installs versioned extensions with declared dependencies, capabilities and integrity evidence.
From content to result
A controlled path instead of loosely connected programs.
A resource retains its identity. Processing creates traceable results and can later be reused as a flow.
- 1→
Open resource
Repository ID and exact revision remain known.
- 2→
Choose a tool
The data type determines suitable viewers and actions.
- 3→
Run a Function
Contract, inputs, permissions and risk are checked.
- 4
Store the result
A new resource or immutable revision is created.
JOBReproducible job with known inputs, versions and results
Use cases
From a single task to a repeatable process.
The entry point is always a concrete task. The same building blocks can later share repository content or run as a flow.
- 01
Use documents and images together
Several tools work with the same resources without uncontrolled file copies.
Import document → Register images as resources → Edit a chosen revision
Dependencies remain exactly traceable - 02
Run one task interactively
A Forge Function is used directly in the Workbench with validated parameters.
Choose Function → Validate inputs → Review result
One recorded and bounded job - 03
Convert a format in the viewer
The data type determines which published converters match the open content.
Open resource → Choose converter → Compare source and result
Original and conversion remain separate - 04
Automate a recurring process
Previously used Functions become typed steps in a Forge Flow.
Connect steps → Set parameters → Publish a versioned flow
Reproducible execution with job history
Technical foundations
Data control and automation remain independently verifiable.
Forge Functions and flows
A Function solves one bounded task and defines its contract independently of the interface.
- Typed inputs and outputs
- Declared capabilities and risks
- Persistent jobs and history
- Reuse in GUI, flow and API
Security and trust model
Extensions receive only explicitly required permissions.
A package receives no blanket access to the operating system, file system or repository. Declaration, validation and execution remain separate control points.
- 01
Declare capabilities
The package states the functional and technical permissions it requires.
- 02
Check access again
The host validates permission and input for every concrete operation.
- 03
Expose risks
Write, move or delete actions can require confirmation of an immutable execution plan.
- 04
Bind artefacts
Versions and executable packages are uniquely associated through integrity evidence.
Approval applies to the concrete operation, not as permanent trust.
Terminology
The essential building blocks at a glance.
Akyao uses precise terms so content, tools and execution do not become conflated.
- Resource
- A domain-identifiable content item with a stable ID, data type and revisions.
- Revision
- An immutable stored state of a resource.
- Forge Function
- A versioned processing step with a typed contract.
- Converter
- A Function that transforms one defined source data type into a target data type.
- Forge Flow
- A versioned directed process of compatible Functions and converters.
- Job
- A persistent record of an execution with inputs, versions, status and result.
Project status
Documentation follows the real product state.
The tool catalogue shows published Functions. Planned extensions remain separate on the roadmap; downloads stay closed until a release is verified.