Blueprint kit One-time purchase Self-serve

Everything in the
box.

You answer a questionnaire about your Mac, your tools, your model access, your privacy boundaries, your ethical preferences, and your workflows. Aksel generates 13 setup files specific to your setup — ready to use, hand to an agent, or implement step by step.

The operating layer

The personal workflow is created by the documents.

An agentic workflow becomes personal when the agent starts from the same operating rules every time: your context, limits, approvals, privacy routing and preferred way of working. The LLM does the reasoning. The harness connects files and tools. The Aksel file pack tells both how to behave.

01

Context and memory

Who you are, how you work, which projects matter, and what the agent should not need explained again.

02

Rules and guardrails

What may be touched, what stays local, when approval is required, and which ethical boundaries should travel with the task.

03

Workflow playbooks

Repeatable steps for useful work, with logging and review so automation stays visible before it becomes trusted.

What Aksel is — and is not.

Aksel is a blueprint product, not a managed service. This boundary is the product.

You are buying the operating foundation, not a finished AI system.

Included

  • 13 generated setup files
  • Compatibility score for your Mac
  • Setup walkthroughs and checklists
  • Agent context files for tools like Claude Code and Codex
  • Privacy routing rules
  • Workflow playbooks and an ROI baseline
  • A local event log template for review and learning

Not included

  • Installation or setup by Aksel
  • Ongoing technical support
  • Managed hosting or platform login
  • Troubleshooting your Mac, models, or third-party tools
  • Custom development or consulting
  • Compliance, legal, or security sign-off
  • A guarantee that agent actions or model providers will behave as expected

You implement the setup yourself, or hand the files to a coding agent. Aksel provides the map — you decide what runs.

The blueprint pack

13 setup files. All yours.

Every file is generated from your questionnaire answers — not a generic template. Simple local files, no proprietary platform, no expiry date.

The questionnaire is where you define what may run locally, what may use cloud AI, which models or subscriptions you have, what the agent must ask before doing, and which ethical boundaries should be written into the setup. If you are unsure, choose Make it work for me and Aksel will start from conservative defaults you can review.

These files are the starting point for workflow automation, not just documentation. They give you the routing rules, playbooks, and agent context to make repeatable multi-step work delegable and auditable from day one.

AI_OPERATING_SYSTEM.md

Your AI OS

The master document. One file that describes your complete local-first AI setup — models, tools, routing rules, and conventions.

AGENTS.md / CLAUDE.md / CODEX.md

Agent context files

Drop these in any project root. Claude Code, Codex, and Cursor read them automatically — they know your conventions before writing a line.

privacy_routing.md

Privacy routing rules

Explicit rules: what runs locally, what can go to cloud AI, and what must never touch AI at all. Based on your data types and risk tolerance.

workflow_playbooks.md

Workflow playbooks

Step-by-step playbooks for your most common AI-assisted work loops — for you to follow, or for an agent to execute.

install_plan.md

Install plan

Ordered install steps for your specific tools and models. No guesswork, no YouTube tutorials — just the sequence that fits your machine.

hardware_check.md

Hardware check

RAM, unified memory, disk, and thermal assessment. Confirms which local models your Mac can run at usable speed.

roi_baseline.md

ROI baseline

A concrete before/after baseline for the workflows you identified — so you can measure whether your AI setup is actually saving time.

maintenance_plan.md

Maintenance plan

A lightweight upkeep checklist: model updates, disk hygiene, context file reviews. Keeps your setup from decaying over time.

trust_manifest.md

Trust manifest

Documents what each tool in your setup is trusted to access — files, APIs, clipboard, network. A record you control.

data_flow.md

Data flow map

A plain-text diagram of how data moves through your setup — which tools see what, and where the privacy boundary sits.

project_event_log.md

Project event log

A local durable log for every agentic project. Records date, actor, goal/prompt, files touched, commands run, model and tool used, decision made, outcome, evidence, risk flagged, and follow-up date. Yours to fill — not monitored by Aksel.

Why the event log matters

Work that happens in the background stays visible.

When an AI agent works without you watching every step — completing tasks, editing files or using connected services — the event log becomes your record of what happened: what ran, who authorised it, what changed, and what should be checked.

Capture eventsEach run gets a dated entry — actor, goal, actions, outcome. No guessing what happened last week.
Review patternsRepeated actions and recurring anomalies surface when you have a log. Promote useful patterns into your context files.
Measure ROICross-reference the log against your roi_baseline.md to see which workflows are actually saving time.
Stay in controlA local file. No sync. No platform. Aksel has no access to it — and never will.

After purchase

Three ways to use the files.

The blueprint pack is designed to be used in whichever mode fits how you work.

Agent
Hand to a coding agent

Drop CLAUDE.md, CODEX.md, or AGENTS.md in your project root. Drop install_plan.md into Claude Code or Codex and ask it to implement. The files are written for this.

Plan
Follow the checklists yourself

Work through install_plan.md and workflow_playbooks.md step by step. Each step is explicit — no assumed context from a tutorial that may be outdated.

Context
Use as a living reference

Keep the files in a folder on your Mac. Edit them as your setup evolves. They are simple local files — no app required, no sync dependency.

Privacy
Share with a consultant or IT

The data_flow.md and trust_manifest.md are written to be readable by a third party — useful if you need approval from IT or a compliance team.

Important — read before you buy

You are buying the instruction file pack, not a guaranteed working system.

Aksel delivers blueprint and setup files. You are responsible for reading and executing any instructions, running any agent actions, granting permissions, connecting tools, and handling all data on your own machine. Aksel has no presence on your system and cannot control what happens when you or an agent acts on the files.

Be aware of the following risks before you proceed:

  • Prompt injection: malicious content read by an AI agent can cause it to take unintended or harmful actions on your machine.
  • Agent commands: if you hand the blueprint to a coding agent, it may run Terminal commands, delete files, modify configuration, or call external APIs.
  • Local file and system damage: incorrect or misapplied instructions can overwrite or delete files, break software, or misconfigure your system.
  • Third-party model and tool changes: AI providers (OpenAI, Anthropic, Google, and others) and open-source projects change their APIs, pricing, and behaviour independently. New models released after purchase are not automatically covered. Existing models may be retired, renamed, or rate-limited without notice.
  • OpenClaw and open-source tool drift: if the Blueprint Pack references OpenClaw or open-source tools, those are separate tools/projects outside the purchased Blueprint Pack unless explicitly included in a future version. Aksel does not warrant they remain maintained, secure, or compatible with future macOS or hardware.
  • Self-modifying agent behaviour: agents that edit their own context or chain further actions can behave unpredictably.
  • User-directed actions: you are responsible for every prompt, goal, permission, API call, automation, and output you initiate or approve after delivery. Aksel does not monitor or control your execution environment after the files are delivered.

Read the full Terms & Risk Notice →