Author

Data Bricklaying Diary

Records practices, thoughts, and pitfalls on the data grunt-work journey, sharing content on data platforms, data analysis, data processing, data governance, knowledge graphs, and more. Less theory, more hands‑on, making complex data technologies simple.

165

Articles

Likes

383

Views

Comments

Latest from Data Bricklaying Diary

100 recent articles max

Data Bricklaying Diary

Oct 6, 2026 · Fundamentals

Mission Engineering 10: Building a Reusable Business Ontology from Coffee Brewing

This article uses coffee brewing as a case study to define a reusable business ontology that distinguishes recipe versions, execution plans, actual brews, records, products, and evaluations, emphasizing traceable instance relationships, versioning, provenance, and constraint validation without conflating plan with actuals.

BFOBusiness OntologyIAO

0 likes · 18 min read

Mission Engineering 10: Building a Reusable Business Ontology from Coffee Brewing

Data Bricklaying Diary

Oct 5, 2026 · Artificial Intelligence

Thin Agent Loop, Thick Control Plane: Why Enterprise AI Agents Need a Stable Harness

This article argues that enterprise AI agents require a robust control plane to manage permissions, persistent task state, side-effect reconciliation, and result verification — separating these concerns from the replaceable agent loop to ensure accountable, recoverable business operations.

AI agentsHarness²Task State Management

0 likes · 17 min read

Thin Agent Loop, Thick Control Plane: Why Enterprise AI Agents Need a Stable Harness

Data Bricklaying Diary

Oct 5, 2026 · Fundamentals

Mission Engineering 08: Modeling Hand-Pour Coffee with OPM — Objects, Processes, and States

This article applies Object-Process Methodology (OPM) to model a hand-pour coffee brewing process, illustrating how to distinguish objects, processes, states, enablers, agents, and transformees, and how to link them to requirements and tasks while identifying resource occupancy gaps.

ISO 19450OPLOPM

0 likes · 31 min read

Mission Engineering 08: Modeling Hand-Pour Coffee with OPM — Objects, Processes, and States

Data Bricklaying Diary

Oct 4, 2026 · Fundamentals

Mission Engineering 07: Baseline First — Test Process Changes Before Buying Gear

This article demonstrates Mission Engineering principles by using a morning coffee routine to show how to establish a baseline, compare isolated process changes (pre-preparation vs. detailed recording), design a run matrix for experimentation, and define abandonment criteria before investing in new equipment.

Alternative AnalysisBaselineCoffee Case Study

0 likes · 25 min read

Mission Engineering 07: Baseline First — Test Process Changes Before Buying Gear

Data Bricklaying Diary

Oct 4, 2026 · R&D Management

Mission Engineering 06: Who Does What, With Which Tools — From Paper Plans to Verified Execution

This article demonstrates how to translate mission tasks into concrete engineering threads by assigning specific people, tools, and actions to each step, using a coffee-making example to expose resource contention, handoff gaps, and the difference between paper parallelism and real-world feasibility.

Execution PlanningHandoff VerificationMEG 2.0

0 likes · 22 min read

Mission Engineering 06: Who Does What, With Which Tools — From Paper Plans to Verified Execution

Data Bricklaying Diary

Oct 3, 2026 · R&D Management

Mission Engineering 05: Turning Vague Requests into Verifiable Requirements

This article demonstrates how to transform ambiguous stakeholder statements like 'make it good, faster, and repeatable' into structured, traceable requirements with explicit conditions, responsibilities, verification methods, and evidence handling, using a coffee-making scenario as a teaching example.

CF-REQMission Engineeringcoffee example

0 likes · 17 min read

Mission Engineering 05: Turning Vague Requests into Verifiable Requirements

Data Bricklaying Diary

Oct 3, 2026 · R&D Management

Mission Engineering: Why Memorizing Steps Fails — Defining Task Inputs, Outputs, and Dependencies

This article uses hand-drip coffee as a case study to demonstrate mission engineering task analysis: decomposing tasks, specifying inputs/outputs/start conditions/completion criteria for each step, linking dependencies via quality gates, handling missing items, and distinguishing material independence from resource contention, all while remaining implementation-agnostic.

Coffee Case StudyDependency MappingImplementation-Agnostic Design

0 likes · 16 min read

Mission Engineering: Why Memorizing Steps Fails — Defining Task Inputs, Outputs, and Dependencies

Data Bricklaying Diary

Oct 2, 2026 · R&D Management

Which Rules Stay When AI Agents Get Smarter? A Framework for Essential Constraints

The article proposes a framework for managing AI agent development rules that retains essential constraints like goals, boundaries, and acceptance criteria while loading project facts and technical guidance per task, and validates rule removal through fixed-task evaluation after model upgrades.

AI agentsClaude CodeModel Evaluation

0 likes · 10 min read

Which Rules Stay When AI Agents Get Smarter? A Framework for Essential Constraints

Data Bricklaying Diary

Oct 2, 2026 · R&D Management

Mission Engineering: Who Decides If the Coffee Is Good? Defining Success Metrics Beyond Timing

This article uses a morning coffee scenario to illustrate mission engineering's three-tier metric framework (MOS, MOE, MOP), showing how to define verifiable success criteria, separate stakeholder acceptance from process completion, and create traceable metric definitions that link overall outcomes to specific performance measurements.

MOPMOSMission Engineering

0 likes · 22 min read

Mission Engineering: Who Decides If the Coffee Is Good? Defining Success Metrics Beyond Timing

Data Bricklaying Diary

Oct 2, 2026 · R&D Management

Mission Engineering 02: Why Weekend vs. Weekday Coffee Requires Separate Scenario Analysis

This article uses pour-over coffee to illustrate mission engineering's scenario and vignette framework, showing how to define participants, goals, time constraints, starting conditions, verified facts, assumptions, and measurement boundaries so that weekend and rushed weekday mornings can be fairly compared and improved.

Assumption TrackingConstraint ManagementMission Engineering

0 likes · 18 min read

Mission Engineering 02: Why Weekend vs. Weekday Coffee Requires Separate Scenario Analysis