Analysis Archive on processkit

processkit v1.0 Base Context

Mon, 01 Jan 0001 00:00:00 +0000

Created: 2026-07-04

This historical base context was created for the processkit v1.0 redesign. It was built from the earlier projectious-work/processkit repository, cloned locally at:

Source URL: https://github.com/projectious-work/processkit
Analyzed commit: 6a9a175f95c42dd76e23488feca42e3d05526b98
Local clone: /tmp/processkit-original

The goal is to preserve the proven v0.x product target while creating a clean basis for processkit v1.0 improvement briefings.

Current Guiding Briefing

The current guiding briefing is processkit-v1.0-rfc-draft.md, analyzed in the processkit v1.0 RFC analysis .

Conflict rule:

preserve the stable product target captured in this base context
use the v1.0 RFC for ontology, branch, release, schema-composition, validation, indexing, and cutover-gate direction
treat concept-mapping-2026-05-16.md as historical input where it agrees with the RFC, not as current guidance where it conflicts

Current Repository Status

At the time of this analysis, the workspace was a fresh aibox/processkit-derived project scaffold, not yet a rebuilt processkit source tree.

Concept Mapping Briefing Analysis

Mon, 01 Jan 0001 00:00:00 +0000

Source: concept-mapping-2026-05-16.md

Analyzed: 2026-07-04

Supersession note: processkit-v1.0-rfc-draft.md is now the guiding briefing for processkit v1.0. Where this analysis conflicts with the processkit v1.0 RFC analysis , the RFC analysis wins. Keep this file as historical interpretation of the earlier concept-mapping input, not as current implementation guidance.

The filename dates the briefing to 2026-05-16, but the document itself continues through Round 17 on 2026-05-20. Treat it as a mid-May design snapshot, roughly six to seven weeks old as of this analysis.

processkit v1.0 RFC Analysis

Mon, 01 Jan 0001 00:00:00 +0000

Source: processkit-v1.0-rfc-draft.md

Analyzed: 2026-07-04

Status for this project: guiding briefing. Where this RFC conflicts with concept-mapping-2026-05-16.md or concept-mapping-briefing-analysis.md , this RFC wins.

Executive Read

The RFC turns the earlier concept-mapping work into an implementation and release proposal. It is no longer just an ontology discussion. It asks upstream processkit maintainers to host a full v1.0 greenfield rebuild on a parallel v1.0 branch while main continues v0.x maintenance.

The product target from the base context remains intact: processkit is still provider-neutral process memory, skills, and MCP tooling for agentic software projects. The RFC changes the model and build plan used to reach that target.

OKF Compatibility Analysis

Mon, 01 Jan 0001 00:00:00 +0000

Source:

Google Cloud announcement, “Introducing the Open Knowledge Format”, published 2026-06-12
GoogleCloudPlatform/knowledge-catalog okf/SPEC.md, v0.1 draft, inspected at d44368c15e38e7c92481c5992e4f9b5b421a801d

Analyzed: 2026-07-04

Recommendation

processkit v1.0 should support OKF as an import/export and publication profile, but should not make OKF the canonical internal format.

In practical terms:

Yes: emit conformant OKF bundles from selected processkit knowledge.
Yes: ingest OKF bundles into processkit as external knowledge sources.
Yes: preserve OKF-compatible affordances in v1.0 schema design where they do not weaken processkit semantics.
No: do not require the whole repository or canonical context/ tree to be an OKF bundle.
No: do not replace processkit entity IDs, typed relations, lifecycle states, validation modes, event logs, or interface-aware queries with OKF’s permissive markdown conventions.

This gives us interoperability without losing the benefits that make processkit more than an LLM wiki.

processkit v1.0 Start Assessment

Mon, 01 Jan 0001 00:00:00 +0000

Analyzed: 2026-07-04

Sources considered:

processkit-v1.0-rfc-draft.md
processkit v1.0 RFC Analysis
Concept Mapping Briefing Analysis
OKF Compatibility Analysis
Google OKF announcement and v0.1 specification
External survey of adjacent agent, memory, metadata, and coding-agent projects

Judgement

The v1.0 plan is good enough to start, but not as an unconstrained 9-12 month greenfield rebuild.

Start a v1.0 branch now, but run it as a narrow alpha first:

prove a small vertical slice before implementing the full ontology
keep processkit’s canonical semantics stricter than OKF
position processkit as process memory and governance, not as another agent runtime
integrate with external runtimes instead of rebuilding them
add OKF import/export as a boundary compatibility feature

The plan’s direction is strong. Its main risk is scope, not concept.