# Composable Architecture

### The problem with upgrading

Adding new features to a live blockchain typically requires a consensus-breaking change that involves a coordinated governance action. 

**This upgrade process introduces major friction to the blockchain development lifecycle and can greatly limit the speed of protocol reform and enhancements.**

{% hint style="warning" %}
How would you upgrade on other stacks? Re-build? Multi-layer governance? Social coordination?
{% endhint %}

### Frictionless additions 

👉 *Rather than growing on a single chain...*

* Canopy chains can transform into an application-specific ecosystem without any governance action. 
* This is a simple process of activating security features and cloning the Canopy blockchain for their new use cases. 
* This process distributes workloads and lessens the reliance on single validator groups.

### Sharding as a feature

* Canopy chains can quickly scale by adding interoperable sibling chains 
* Horizontal clones enable a distribution of workload, lessening the reliance on single validator groups

<figure><img src="/files/7o6VSOLyfSz4nkcZAfct" alt=""><figcaption></figcaption></figure>

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://canopy-network.gitbook.io/docs/canopy-network/core-features/composable-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.