Consuming

Consuming in Typeflows means configurations become versioned dependencies you declare and automatically receive, rather than static files you copy and paste. This moves configuration management from manual labour to automated dependency resolution.

A Different Approach

Typeflows treats configurations as dependencies that can be declared, resolved, and automatically updated similar to code libraries.

When you consume a Typeflows package, you’re importing versioned configuration objects that can evolve, improve, and propagate updates across your entire organisation.

Configuration as Versioned Assets

Typeflows packages live in artifact repositories alongside your code dependencies. They follow semantic versioning, can have their own dependencies, and evolve independently from the projects that consume them.

This creates a marketplace of configuration knowledge where:

• Security improvements propagate automatically to all consuming projects
• Best practices discovered by one team benefit the entire organisation
• Community expertise gets encoded once and shared everywhere
• Configuration complexity is managed by specialists, consumed by everyone

The Network Effect

When configurations become consumable packages, they create network effects similar to open source software. The most useful patterns get adopted widely, improved collectively, and become more robust through widespread use.

Organisations develop internal ecosystems of configuration packages:

• Foundation packages that encode company-wide policies and standards
• Platform packages that configure specific deployment environments
• Domain packages that capture team-specific expertise and requirements

This enables community packages that solve common problems across industries, creating shared solutions that benefit everyone.

Building Blocks for Composition

Consumed packages don’t just provide static configurations - they become Typeflows objects that can be composed. This enables a layered approach where you combine:

• Organisational standards from company packages
• Platform requirements from infrastructure packages
• Application patterns from framework packages
• Project customisations from local code

The consuming model enables composition by providing reliable, versioned building blocks that can be combined to create project-specific solutions.

From Isolation to Ecosystem

Consuming changes configuration management from isolated projects copying files to connected ecosystems sharing knowledge. Projects become participants in a broader configuration community rather than starting from scratch.

This shift enables the same collaborative development patterns that made open source software successful: distributed expertise, community contributions, and automatic propagation of improvements across the entire ecosystem.

When everyone consumes shared configurations, configuration management becomes as mature and reliable as software development itself.