agiwork.

AGIWORK / FIELD GUIDE

Build the ecosystem.
Keep it purposeful.

A practical guide to the layers, choices and tools behind an enterprise AI platform — from a first experiment to managed operations.

MY APPROACH

Start small. Add capability only when a real requirement justifies it.

THE IDEA / FROM MY REFERENCE ARCHITECTURE

One ecosystem.
Different starting points.

I use this map to separate the jobs an AI platform has to do: serving people, connecting models and knowledge, controlling access, and operating safely. The toolkit below is an adapted selection from my enterprise AI ecosystem catalogue.

You do not need every component. Begin with a defined use case and add layers as data sensitivity, users and operational requirements grow. The stages are a learning path, not a maturity certification or a prescription.

02 / A LEARNING PATH

From first experiment
to reliable delivery.

I group tools by the work you are doing. Some tools serve several stages; a later stage is not automatically better.

03 / TOOLKIT

Choose by job,
not by popularity.

Official project links are starting points for evaluation. These projects overlap and evolve; check current releases, compatibility, maintenance, security and licence terms before adoption.

THE COMPLETE COLLECTION

Explore the wider agent ecosystem.

Browse my full directory by architecture role, from personal assistants and coding agents to models, knowledge and operations.

Explore all projects ↗
01 / START

Interfaces & first experiments

Give people a useful way to interact with a model and learn from a small, bounded use case.

MY TAKEStart with one interface and one model. A self-hosted interface does not automatically make an external model or its data processing private.

02 / BUILD

Agents & orchestration

Build a single agent or workflow with an explicit task, tools, state and clear boundaries.

MY TAKEA model runtime, an agent framework and a workflow engine have different jobs. Choose the simplest fit; multi-agent coordination is not a prerequisite.

AI & agent interface

Open WebUI

Configure assistants and connect models, tools and knowledge through a self-hosted interface.

Source-available; review licence and branding terms.
Agent & workflow automation

n8n

Create AI agents and automated workflows with visual building blocks.

Fair-code; review the Sustainable Use License.
Personal agent platform

OpenClaw

Run a personal assistant that connects models, tools and messaging channels.

Review workspace permissions and access to connected accounts.
Personal agent platform

Hermes Agent

Run a tool-using assistant with persistent context, skills and messaging integrations.

Review skills, tool access and the selected model provider.
Personal agent framework

nanobot

Build or run a lightweight personal agent with tools, memory and chat integrations.

Review exposed tools, credentials and deployment settings.
Agent library

smolagents

A lightweight Python starting point for tool-using agents.

Code-executing agents require isolation.
Visual agent builder

Flowise

Compose AI and agent workflows through a visual interface.

Review community and commercial editions separately.
Agent framework

Pydantic AI

Python agents with typed inputs, outputs and validation.

Check model and provider terms.
Stateful orchestration

LangGraph

Build stateful, controllable agent workflows.

Review related service editions.
Multi-agent framework

CrewAI

Coordinate agents and tasks where roles and handoffs are useful.

Review core and hosted offerings separately.
Agent toolkit

Google ADK

A code-first toolkit for building and evaluating agents.

Cloud integrations may have separate terms.
02 / BUILD

Coding agents & development harnesses

Give development agents a bounded workspace to inspect code, propose changes, run tools and support delivery.

MY TAKEA coding agent combines a model with an execution harness and tools. Compare workspace permissions, model access, review workflows and data handling before adoption.

02 / BUILD

Documents, retrieval & knowledge

Turn approved source material into searchable evidence that an application can cite.

MY TAKEFor RAG, check extraction quality, access permissions, retrieval relevance and source freshness. A vector database is not an access-control system by itself.

02 / BUILD

Audio, images & model development

Add media processing or adapt a model when the problem actually requires it.

MY TAKEStart with existing models and a test set. Fine-tuning, visual workflows and transcription introduce additional compute, data and model-licence decisions.

03 / INTEGRATE

Model gateways & serving

Route applications to approved local or external models, and select serving infrastructure appropriate to demand.

MY TAKEOllama is a useful local starting point. vLLM and KServe address different serving and deployment needs; benchmark on your own hardware and models.

03 / INTEGRATE

Tools, APIs & workflows

Connect approved systems through controlled interfaces, and make long-running actions observable and recoverable.

MY TAKEMCP is a protocol, not a security boundary. Use least-privilege credentials, approval for consequential actions and isolation for untrusted execution.

03 / INTEGRATE

Identity, policy & guardrails

Protect access to the platform, models, data and tools using several complementary controls.

MY TAKEIdentity, secrets, authorization, data protection and AI guardrails are separate layers. No prompt filter alone prevents every injection or data leak.

04 / OPERATE

Evaluation & AI security

Test both useful behaviour and failure modes before expanding access or autonomy.

MY TAKECreate a representative test set and inspect retrieval, answers, permissions, unsafe tool calls and regressions. Human review remains important for consequential actions.

04 / OPERATE

Tracing, metrics & operations

Make model calls, tool use, latency, errors and operational costs visible to the teams responsible.

MY TAKETracing may contain sensitive inputs or outputs. Minimise logged data, control access and define retention before using production data.

04 / OPERATE

Governance, catalogues & costs

Assign owners and policies to data, models and services; make adoption and cost decisions reviewable.

MY TAKEA data catalogue, a policy engine and a cost monitor support governance but do not create compliance by themselves. Controls depend on the organisation and jurisdiction.

LICENSING / IMPORTANT DISTINCTION

Every project has its own terms.

I track the licences and product terms for the projects in this architecture and my agent directory. A repository licence does not automatically cover hosted services, dependencies, models, weights or datasets. Check the exact version and use case.

Project licence sources checked 2026-10-29. Standard labels reflect the reviewed root licence and GitHub's identification; exceptions and uncertainties are stated explicitly.

Some important distinctions

open-webui

Open WebUI License

Branding rules apply from v0.6.6; earlier code and small deployments have different terms.

Source ↗

n8n

Sustainable Use / Enterprise

Community and enterprise code have different terms; hosted access, white-labeling and client workflow editing require review.

Source ↗

dify

Modified Apache-2.0

Additional conditions address multi-tenant service and frontend branding.

Source ↗

AutoGPT

MIT / Polyform Shield

The platform directory uses Polyform Shield; other repository portions use MIT.

Source ↗

multica

Multica License

Modified Apache terms restrict some hosted or embedded third-party offerings; review branding conditions.

Source ↗

SDV

Business Source License 1.1

Synthetic Data Service use is restricted; each release transitions to MIT on its change date.

Source ↗

ZCode

ZCode Terms of Service

The published terms restrict commercial use unless a qualifying subscription or separate agreement applies; check section VI.

Source ↗

OpenAI Codex

Apache-2.0 harness / service terms

The Codex repository uses Apache-2.0; OpenAI services, models and subscriptions have separate terms.

Source ↗
Explore all 181 project licence records

Filter by project or licence type. This is a starting point for reviewing the actual terms, not a licence grant or a substitute for checking the relevant artifacts.

181 records

Adala

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

adk-python

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

ADR

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

ag-ui

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

agency-swarm

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Agent Skills

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

agent-framework

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

agent-orchestrator

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

agent-second-brain

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

agent-zero

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

AgentGPT

GPL-3.0

Review source and licence obligations when distributing covered software.

Source ↗

agents-cli

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

agno

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

aider

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Airbyte

Elastic License 2.0

Review the restrictions in Elastic License 2.0, including limits on managed services.

Source ↗

airi

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

anthropic-sdk-python

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

AstrBot

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

atomic-agent

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

autogen

MIT code / CC BY 4.0 docs

Code and documentation are licensed separately; review the relevant files.

Source ↗

AutoGPT

MIT / Polyform Shield

The platform directory uses Polyform Shield; other repository portions use MIT.

Source ↗

AutoResearchClaw

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

babyagi

MIT declared; file unavailable

The README states MIT, but its linked root licence file was not found in this check.

Source ↗

bb

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

beeai-framework

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

BrowserOS

AGPL-3.0 / component licences

The main licence is AGPL-3.0; browser patches and other components may have separate licences.

Source ↗

camel

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

cccc

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

ChatDev

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Choir

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

claude-code

Commercial terms

The repository licence reserves rights and refers to Anthropic commercial terms.

Source ↗

ClawTeam

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

CLI-Anything

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

codebuddy

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

ComfyUI

GPL-3.0

Review source and licence obligations when distributing covered software.

Source ↗

CopilotKit

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

crewAI

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

crush

FSL-1.1-MIT

Functional Source License applies first; each version changes to MIT on its specified change date.

Source ↗

DB-GPT

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

deepagents

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

DeepCode

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

DeepResearch

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

deepseek-harness

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

DeepSeek-Reasonix

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

DeepTutor

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

deer-flow

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

dify

Modified Apache-2.0

Additional conditions address multi-tenant service and frontend branding.

Source ↗

Docling

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

E2B

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

eigent

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

eliza

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

FastCode

MIT declared; file unavailable

The README states MIT, but its linked root licence file was not found in this check.

Source ↗

FFmpeg

LGPL / GPL; build-dependent

Licence obligations depend on the enabled components and build options.

Source ↗

Firecracker

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Flowise

Apache-2.0 / Commercial

Most code is Apache-2.0; enterprise directories and specifically marked files have commercial terms.

Source ↗

FreeToken

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

fx

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

garak

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

goclaw

CC BY-NC 4.0

The repository licence restricts commercial use; verify the exact scope.

Source ↗

gollem

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Google Antigravity

Google Antigravity terms

Service and enterprise access may be subject to different Google agreements.

Source ↗

gpt-researcher

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Gradio

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Grafana

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

Harbor

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

haystack

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

hermes-agent

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

hexstrike-ai

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Hugging Face TRL

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

ironclaw

MIT OR Apache-2.0

The project offers a choice between MIT and Apache-2.0; check the version and included components.

Source ↗

JupyterHub

BSD-3-Clause

Retain required notices and observe the non-endorsement condition.

Source ↗

Keycloak

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

kilocode

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

kodacode

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

KServe

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

LabClaw

MIT declared; file unavailable

The README states MIT, but its linked root licence file was not found in this check.

Source ↗

langchain

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Langfuse

MIT / Enterprise

MIT applies outside the enterprise directories; those directories have separate terms.

Source ↗

langgraph

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

langroid

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

langsmith-cli

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

letta

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

LibreChat

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

LiteLLM

MIT / Enterprise

The root licence distinguishes MIT code from enterprise-directory terms.

Source ↗

llama.cpp

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

llama_index

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

llm-wiki-v2

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

llmware

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

local-deep-research

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

LocalAGI

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

MetaGPT

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Microsoft Presidio

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Milvus

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

MiMo-Code

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

mini-swe-agent

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

MiroFish

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

ml-intern

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

mlflow

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Model Context Protocol

Apache-2.0 / MIT / CC BY 4.0

The specification repository is transitioning licences; documentation and some contributions have different terms.

Source ↗

moltis

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Moodle

GPL-3.0

Review source and licence obligations when distributing covered software.

Source ↗

ms-agent

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

MTPLX

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

multica

Multica License

Modified Apache terms restrict some hosted or embedded third-party offerings; review branding conditions.

Source ↗

n8n

Sustainable Use / Enterprise

Community and enterprise code have different terms; hosted access, white-labeling and client workflow editing require review.

Source ↗

nanobot

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

NATS

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

NeMo Guardrails

Apache-2.0

Retain required notices and check licence terms for models and third-party components.

Source ↗

Neo4j Community

GPL-3.0

Review source and licence obligations when distributing covered software.

Source ↗

NeuralDeskApp

ValeDesk Community License

The community licence includes a revenue threshold and competition restrictions.

Source ↗

Node-RED

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

oasis

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

oh-my-pi

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

ollama

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

onyx

MIT / Enterprise

Most repository content is MIT; enterprise directories have separate terms.

Source ↗

Open Policy Agent

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

open-webui

Open WebUI License

Branding rules apply from v0.6.6; earlier code and small deployments have different terms.

Source ↗

OpenAgentsControl

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

OpenAI Codex

Apache-2.0 harness / service terms

The Codex repository uses Apache-2.0; OpenAI services, models and subscriptions have separate terms.

Source ↗

OpenBao

MPL-2.0

Review file-level source obligations when distributing modified covered files.

Source ↗

openclaw

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

opencode

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

OpenCost

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

openfang

MIT / Apache-2.0 files

Both licence files are present; verify the terms for the component and release you use.

Source ↗

openhuman

GPL-3.0

Review source and licence obligations when distributing covered software.

Source ↗

OpenIntelligentUI

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

openinterpreter

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

OpenJarvis

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

OpenMetadata

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

OpenResearch

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

OpenSandbox

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

openscience

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

OpenSearch

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

OpenTelemetry

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

openwork

MIT / Enterprise

Most repository content is MIT; the enterprise directory has separate terms.

Source ↗

opik

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

owl

Apache-2.0 declared; no root file

The README states Apache-2.0; a root licence file was not found in this check.

Source ↗

paperclip

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

pentagi

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

pgvector

PostgreSQL License

Permissive licence; retain the required copyright and disclaimer notices.

Source ↗

pi

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

picoclaw

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

PolyStrata

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

pool

Product EULA

Use of the product is governed by Poolside’s end-user agreement.

Source ↗

PraisonAI

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

prime-agent

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Prometheus

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

promptfoo

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

pydantic-ai

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Qdrant

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

qm

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

QwenPaw

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

ragflow

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

React

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

SDV

Business Source License 1.1

Synthetic Data Service use is restricted; each release transitions to MIT on its change date.

Source ↗

semantica

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

SGLang

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

sgr-agent-core

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Sigstore Cosign

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

Sipp

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

SkillOS

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

smolagents

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

SoL-Pi

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

storm

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

strix

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

SuperAGI

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

swarm

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

T3MP3ST

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

taskade

Product terms / repository content

The repository covers documentation and press materials; the application has separate terms.

Source ↗

Temporal

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Tesseract

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

tinyagi

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

topsha

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

transformerlab-app

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

Trivy

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

UI-TARS-desktop

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

vllm

Apache-2.0

Retain required notices, mark changes and review the patent provisions.

Source ↗

waku-agent

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

Whisper

MIT

Keep the copyright and licence notice when distributing copies.

Source ↗

worldmonitor

AGPL-3.0

Review distribution and network-source obligations for modified covered software.

Source ↗

ZCode

ZCode Terms of Service

The published terms restrict commercial use unless a qualifying subscription or separate agreement applies; check section VI.

Source ↗

GitHub’s licence identification checks a repository licence file; it does not assess dependencies or every component. How GitHub identifies licences ↗

04 / PRACTICAL GUIDE

Turn the map
into a plan.

These patterns are starting points to investigate, not tested integrations or production-ready blueprints.

01 / KNOWLEDGE ASSISTANT

Answer from approved documents

Start with a small set of permitted documents. Parse and inspect them, index content for retrieval, and build an answer workflow that can cite sources.

Example components: Docling + pgvector or Qdrant + Haystack. Enforce user access at retrieval; test relevance, citations, stale data and unsupported answers.

Explore knowledge tools ↗
02 / CONTROLLED AGENT

Automate a bounded task

Define the task, permitted tools, stopping conditions and a human approval step for consequential actions. Start with read-only access where possible.

Example components: an agent framework + approved APIs or MCP tools + a workflow engine when durability is needed. Isolate code execution and review external tools.

Explore agent frameworks ↗
03 / ORGANISATIONAL ROLLOUT

Make ownership visible

Record the owner, intended users, data classification, model/provider, permissions, evaluation set and operational budget before broader use.

Before expansion: define access control, rollback, monitoring, incident response, data retention and a review process for versions and licences.

Explore operations ↗
Playbook / document question answering

Goal: answer a bounded set of questions using only documents the requester is allowed to access.

  1. Define the scope. Choose an owner, a representative set of questions, approved documents and the access rules for each user group.
  2. Prepare the corpus. Parse and inspect files; use OCR where appropriate. Keep source references and permission metadata alongside each indexed passage.
  3. Build retrieval. Select an embedding model and index, enforce permissions before results reach the model, and test whether relevant passages are retrieved.
  4. Generate with evidence. Ask for source citations and an explicit response when evidence is insufficient. Treat document text as untrusted input, not instructions to the agent.
  5. Evaluate and operate. Test correct answers, misleading documents and cross-user access. Monitor failures, source freshness, latency and cost; decide who reviews errors.
Explore document and retrieval tools ↗
Playbook / model and tool admission

Goal: introduce a model or agent tool through a reviewable process before wider deployment.

  1. Identify the artifact. Record its owner, version, origin, intended task, dependencies and whether it runs locally or uses a provider.
  2. Review terms and data. Check licences for code, model weights and services. Assess data classification, retention, access and provider exposure.
  3. Test in isolation. Evaluate a representative task set, resource needs, misuse cases and failure behaviour. Inspect external skills, tool permissions and dependencies.
  4. Approve and release. Define an accountable owner, access policy, human review for consequential actions and an approved, versioned artifact.
  5. Monitor and revise. Track quality, latency, incidents and cost. Keep a rollback path and repeat review when the model, tool or use case changes.
Explore evaluation and security tools ↗

CHOOSING A STARTING POINT

Prefer the smallest viable stack.

Vector search: pgvector can fit an existing PostgreSQL deployment; a dedicated engine such as Qdrant or Milvus may be worth evaluating for different scale, filtering or operational needs. Test with your own corpus and permissions.

Model hosting: Ollama supports local experimentation; vLLM focuses on serving inference; KServe manages model serving on Kubernetes. These solve overlapping but different problems.

Open software vs. open weights: a permissive code licence does not automatically cover model weights, datasets, plugins or provider services. Check the exact versions and intended use.

External skills and tools: inspect and pin versions, test in isolation, and approve them before promotion to an internal catalogue. Limit runtime permissions and log consequential tool use; a registry is not a substitute for review.

CONTINUE EXPLORING

Build with clarity.

For a wider view of agent tools, explore my public directory. For an architecture conversation, connect with me.