The Subscription Ladder, Worked: From Free Tier to Rent-to-Own
The Subscription Ladder, Worked: From Free Tier to Rent-to-Own The tiered pricing model (S6.8) described the platonic access architecture; the rent-to-own model (S6.3) described ownership; this is the worked example…
The Client Wiki, Worked: Knowledge-to-Wiki Bridge in Practice
The Client Wiki, Worked: Knowledge-to-Wiki Bridge in Practice The knowledge-to-wiki bridge (BR.6) described turning the vault's knowledge into a client wiki; this is the worked example. The client wiki is…
Team Augmentation, Worked: Capability-to-Team Bridge in Practice
Team Augmentation, Worked: Capability-to-Team Bridge in Practice The capability-to-team bridge (BR.5) described team augmentation as an offer; this is the worked example. Team augmentation is the skill product (EX-2) aimed…
Managed Observability, Worked: Monitoring as a Service
Managed Observability, Worked: Monitoring as a Service The monitoring-to-service bridge (BR.7) translated the observability layer into an offer; this is the worked example. Managed observability is the fleet's vital signs…
The Reference Architecture, Worked: Stack as Blueprint
The Reference Architecture, Worked: Stack as Blueprint The stack-to-architecture bridge (BR.11) established the reference architecture as a deliverable; this is the worked example. The reference architecture is the sovereign stack…
The Advisory Retainer, Worked: Strategic Sensing as a Service
The Advisory Retainer, Worked: Strategic Sensing as a Service The sensing-to-advisory bridge (BR.10) translated the research pipeline into an offer: strategic advisory. The advisory retainer is the worked example —…
The Studio Retainer, Worked: Visual Production as a Subscription
The Studio Retainer, Worked: Visual Production as a Subscription The studio retainer (S6.15) was the article; this is the worked example. The studio (S9 series) produces the visual language of…
The Migration Service, Worked: Moving Clients From Cloud Rent to Ownership
The Migration Service, Worked: Moving Clients From Cloud Rent to Ownership The migration service (S6.11) was the article; this is the worked example. The sovereign-stack promise is that customers can…
Security Review as a Service, Worked: The Audit Engagement
Security Review as a Service, Worked: The Audit Engagement The security series (S7) produced the hardening knowledge; the threat-to-review bridge (BR.9) translated it into an offer. Security review as a…
White-Label Publishing, Worked: Their Brand, Our Pipeline
White-Label Publishing, Worked: Their Brand, Our Pipeline White-label publishing (BR.8) is the content bridge in service form: the client's brand on the masthead, our pipeline producing the posts. The content…
Bridges as Services, Worked: Selling the Integration Layer
Bridges as Services, Worked: Selling the Integration Layer The BR series documented bridges as content — the articles that connect two clusters. The business translation is bridges as services: the…
shop.lucidhive.com, Worked: The Marketplace as a Business Model
shop.lucidhive.com, Worked: The Marketplace as a Business Model The agent-run marketplace (SECTOR07a-37) is the sovereign stack's most ambitious business surface: a shop where agents are both vendors and buyers (SECTOR07a-42)…
The Client Dashboard, Worked: Self-Service Portal as Revenue Engine
The Client Dashboard, Worked: Self-Service Portal as Revenue Engine The customer dashboard (S6.7) was designed as a portal; the SECTOR07a futures round showed it as a revenue engine (SECTOR07a-40). This…
The Skill Product, Worked: Packaging Capability, Not Output
The Skill Product, Worked: Packaging Capability, Not Output The kingdom sells capability, not output (SECTOR07a-39): a client does not buy articles, dashboards, or reports — they buy the skill that…
Backup Cadence for the Sovereign Stack: Restore-First Thinking
Backup Cadence for the Sovereign Stack: Restore-First Thinking Backups are not copies; backups are promises. The sovereign stack's promise is that nothing is lost — the vault, the graph, the…
The Health-Check Pattern: Probing Agents Before They Work
The Health-Check Pattern: Probing Agents Before They Work A fleet should not discover its agents are broken while they are working. The health-check pattern is the discipline of probing agents…
Log Hygiene: Structured Output From Every Agent
Log Hygiene: Structured Output From Every Agent A fleet of agents generates a flood of logs; the question is whether the flood is data or noise. Log hygiene is the…
The Ops Playbook for Content Pipelines: Batch Discipline
The Ops Playbook for Content Pipelines: Batch Discipline The content pipeline (S12 series) publishes at scale — batches of articles, images, and metadata moving through a machine. Batch discipline is…