Skip to content
Tagged articles

contract design

6 articles · Page 1 of 1
Digital Deification
Digital Deification
Nov 4, 2026 · R&D Management

FDE Performance Contracts: Four-Zone Responsibility Framework to Prevent One-Sided Blame

The article proposes a four-part framework for structuring FDE performance-based contracts: define FDE-controllable technical delivery, exempt client-side uncontrollable variables (master data, processes, resources, legacy systems), manage gray areas via written risk acknowledgments, and implement practical mechanisms like baseline testing, cooperation dashboards, tiered incentives, and neutral verification.

FDER&D managementcontract design
0 likes · 12 min read
FDE Performance Contracts: Four-Zone Responsibility Framework to Prevent One-Sided Blame
Data Bricklaying Diary
Data Bricklaying Diary
Nov 1, 2026 · Backend Development

Why MCP and Workflows Aren't Enough: Defining Business Action Contracts

The article explains why Model Context Protocol (MCP) and workflows alone cannot enforce business rules like parameter provenance, approval validation, idempotency, and result verification, using a procurement example to illustrate the need for explicit Action contracts that define conditions, approvals, and error handling.

Business ActionIdempotencyMCP
0 likes · 16 min read
Why MCP and Workflows Aren't Enough: Defining Business Action Contracts
Code Archaeology
Code Archaeology
Oct 14, 2026 · Backend Development

Evolutionary Architecture Structure: Connascence, Architectural Quanta, and Contract-Driven Design

This article explores how software topology determines evolvability through connascence-based coupling analysis, architectural quanta as independently deployable units, contract spectra from strict RPC to loose key-value, microservices as evolutionary templates, data mesh for analytical data, and evolutionary database practices including Expand/Contract migrations and data governance.

Bounded ContextDatabase Migrationarchitectural quantum
0 likes · 56 min read
Evolutionary Architecture Structure: Connascence, Architectural Quanta, and Contract-Driven Design
Thought Artisan
Thought Artisan
Aug 8, 2026 · Fundamentals

Why Software Architecture Is Hard: 8 Core Trade-offs from 'The Hard Parts'

This article reviews 'Software Architecture: The Hard Parts', highlighting eight key architectural challenges including trade-offs, data-architecture tensions, service granularity, database decomposition, distributed data access, contract design, code reuse, and error handling in distributed systems.

contract designdatabase decompositiondistributed systems
0 likes · 7 min read
Why Software Architecture Is Hard: 8 Core Trade-offs from 'The Hard Parts'
Xiaokun's Architecture Exploration Notes
Xiaokun's Architecture Exploration Notes
Nov 2, 2025 · Backend Development

Why Strict and Loose Contracts Matter in Microservice Architecture

This article explores the role of contracts in software architecture, explaining why architectural-level contract decisions are crucial, comparing strict and loose contracts such as gRPC, REST, and key‑value formats, and introducing consumer‑driven contracts, their trade‑offs, and practical guidelines for reducing coupling and brittleness in microservices.

Consumer-Driven ContractsRESTcontract design
0 likes · 15 min read
Why Strict and Loose Contracts Matter in Microservice Architecture