
From blueprint to spec lock: how design ownership determines supply chain allocation
Control Shift
This system is simple. You either own the spec or you run the line. Assembly scales volume. It absorbs millions. The contract follows the design file, not the factory floor—a position Rajeev Chandrasekhar, former Minister of State, Electronics & IT, has consistently pushed in framing design-led control. When cost shifts or geography changes, assembly lines are abandoned overnight. Spec control holds the contract. If you define the spec, you dictate the components. If you dictate the components, you cannot be swapped out.
Autopsy of Assembly Without Control
Look closely at the first wave of the domestic electronics manufacturing boom. The state scaled capacity at an unprecedented velocity. Yields held firm. Factories hit their output targets with precision. Yet the foundational architecture remained entirely external. The product was defined upstream while the factory executed downstream—exactly the gap that Satya Gupta, President, VLSI Society of India, has warned about in product ownership. As supply chain shocks eased, the allocation shifted back to incumbents. The shells stayed. The machines stayed. The orders didn’t. That’s execution without leverage.
System Anchor
A hardware contract is not standalone. The chip defines the system. The system defines the product.
Ajit Manocha is blunt: control sits at the architecture. Supply chains allocate through system control, not factory count. Assembly executes. Design allocates. Whoever owns the spec anchors the chain. Without the system node, you are renting capacity.
Conflict Layer
The system runs on three clocks. Product runs twelve to eighteen months. Devices create demand. Components follow. Miss the window, and the spec locks elsewhere. Design runs two to three years. Architecture decides what gets built. Infrastructure runs seven to ten years. Capital locks before output shows up—a constraint Suman Bery, Vice Chairman, NITI Aayog, has repeatedly flagged in capital sequencing. Scale comes after the system. You don’t get all three. Pick wrong, and you lose the allocation.
Product cycle
12–18 months
Devices create demand. Miss the window — spec locks elsewhere.
Design cycle
2–3 years
Architecture decides what gets built.
Infrastructure cycle
7–10 years
Capital locks before output shows up.
Blueprint
Volume doesn’t hold contracts. Spec does. Build products that pull the chain, not components that wait for it. Incentives that don’t lock design ownership don’t hold contracts. Sequence capital where it compounds, not where it locks. Scale without allocation turns capital into a fixed cost.
Cost Threshold
If a nation loses the spec, it loses the allocation. Lost allocation immediately creates idle capacity. Miss one cycle at scale, and a multi-billion-dollar facility turns into stranded capital. Yield cannot save a factory that does not control the spec.
Solutions Spotlight
- →Fund design before fabs.
- →Tie procurement to domestic spec.
- →Force OEMs onto local architecture.
Strategy Note
- —Own the system layer.
- —Fund the design node first.
- —Let manufacturing follow the spec.
Key Takeaway
Laws That Hold The Contract
Analysis series · Issue 4 · India Front
Law I · Design · You are here
Spec Decides. Factories Follow.
Cost gets you in. Control keeps the contract.
Law II · Power
Miss Power. Lose the Line.
Stability holds output. Output holds contracts.
Law III · Precision
Miss Tolerance. Lose the Contract.
Quality isn’t a range. It’s a gate.
Law IV · Production
Nothing Fails For The First Time In Production
Discover it in production, you designed it wrong.
Edition Close · Delivery
No SLA. No Order.
Delivery holds the contract. Miss the cycle, and it reallocates.
