Adjacent-tool migration assessment

2 min readReferenceUpdated 2026-05-19

What you'll find here

The AdjacentToolMapping and AdjacentToolMigrationAssessment contracts that describe how concepts from nearby tools map into Craik before an importer is built.

Assessment, not import.

An assessment is an evidence-backed compatibility record that can later feed import dry-run reports, migration maps, and bridge decisions.

Records

Contract

Records

Fields

AdjacentToolMapping

per concept

Source concept · target Craik concept (project / task / memory / skill / config / receipt) · support level (supported / partial / unsupported) · notes · required controls · unsupported fields.

AdjacentToolMigrationAssessment

per tool

Assessment id · tool name · overall support level · mappings · security notes · redaction requirement · policy envelope id · evidence ids · receipt ids.

Compatibility

Supported

Can be converted without losing Craik's policy, evidence, receipt, and redaction model.

Partial

Needs operator review. Unsupported fields must be named so a dry run can warn without mutating state.

Unsupported

Should not be imported. Secrets and credentials should be reconfigured by an operator, not copied.

What's next

ReferenceImport dry-run reportsHow an assessment becomes a reviewable dry run.ReferenceMigration mapsField-level mapping for memory, skill, and config imports.ReferenceAdjacent runtime bridgeThe runtime-level bridge contract.