Autonex Group
The guiding question for this context file
"What is true of every business within the Autonex Group?"
Every piece of information you include should be answerable with "yes, this applies to everything in this branch." If it only applies to some children, it belongs lower down the tree. If it repeats something already in a parent file, leave it out.
What to include
- ✓Group-wide values, principles, and operating norms that every business is expected to follow
- ✓Shared governance — how decisions escalate, how businesses relate to group leadership
- ✓Shared platforms or infrastructure that all businesses use (e.g. identity, data platform, SSO)
- ✓Group-level strategy and investment priorities that shape what all businesses are working towards
- ✓The Autonex portfolio thesis — why these businesses belong together and what the group is trying to become
- ✓Compliance, legal, or regulatory constraints that apply across all markets and entities
What to avoid
- ✕Details that apply only to one business — those belong in that business's own context file
- ✕Operational specifics like team structures, tooling choices, or product roadmaps
- ✕Content that changes frequently — this file is a stable anchor for all agents
Examples of good context sentences
"All Autonex businesses operate under a shared data governance framework and must comply with the group's GDPR data handling policy."
"Autonex's group strategy is to build the leading European automotive marketplace ecosystem by connecting buyers, sellers, and dealers across all markets."
General principles
🌲
Tree-aware: Agents receive all ancestor files too. Don't repeat what's already above you in the tree.
⏱
Stable, not live: Write things that stay true for months. Roadmap items, sprint tasks, and current incidents belong elsewhere.
🤖
Agent-first: Write as if briefing a capable colleague who has never worked here. Be explicit; don't assume implied knowledge.