-
Notifications
You must be signed in to change notification settings - Fork 10
Vision
priyam-jain-2002 edited this page Aug 23, 2026
·
2 revisions
Lineage exists to make useful agent environments distributable.
Today, a working agent workflow is often scattered across prompts, skills, helper files, notes, local trackers, provider-specific setup, and undocumented conventions. That makes it hard to share the workflow with another person without either leaking private data or forcing them to rebuild the environment by hand.
Lineage focuses on the distribution layer:
agent environment -> safe package -> inspectable receiver-owned activation
- A creator can package a prepared agent environment.
- A receiver can inspect the package before enabling it.
- A non-coder receiver can use a package page or bootstrap prompt instead of learning every CLI command first.
- Setup can create safe local resources with permission.
- Secrets and private machine-local state are not shared.
- Provider-specific behavior stays behind clear adapter boundaries.
- The receiver runs the workflow with their own local agent tools.
Lineage is not trying to become the agent provider. It is not a billing platform, cloud runtime, vector database, or general workflow language.
The long-term value is trust: a package should be understandable, portable, and safe enough that another person can activate it without being a programmer.