Field notes

Engineering SI systems that remain inspectable under change.

Writing on capability versioning, source-aware interfaces, evaluation evidence, bounded actions, and the architecture required to make SI useful inside serious software systems.

Featured engineering note

Capability is not authority.

A capability describes how work could be performed. Authority is a separate decision about one exact consequential action. The distinction keeps configuration from silently becoming permission.

Read engineering note

2026-10-049 min read

Engineering SI capabilities that can change safely

How versioned SI capabilities, dependency records, evaluation evidence, and explicit authority boundaries make system change reviewable.

Capability Engineering / Evaluation / Governance

Read field note

2026-10-0410 min read

Integrating SI with existing systems while preserving the source of truth

A practical architecture for source-aware data, interface contracts, bounded actions, and unknown states when SI works alongside existing systems.

Systems Integration / Source-Aware Data / SI Architecture

Read field note