Skip to content

Provide guidance for adapting the general model to a team's specific approach #9

Open

Description

@mindsocket

Guidance for

  • aliases - "we call them focus areas, not goals"
  • conventions and cadence
    • "we have group goals, then per product objective goals, then per team KRs" (not a recommended approach, but you get the idea)
    • "we plan quarterly, teams propose opportunities in response to group goals, and those opps need to meet x quality conditions"
    • "all in-progress opportunities have an Atlas project and weekly status updates; the decisions, risks etc all get captured there"

Possibly also an entity that encapsulates these things so they can form part of the operating system, and tooling can help with communicating, enforcing, and refining.

Activity

  1. modified the milestones: , on Feb 26, 2026
  2. mindsocket commented on Feb 26, 2026

    @mindsocket
    OwnerAuthor

    Following research on #3 (findings in docs/torres-alignment-research.md):

    Type aliases (#14) are the key mechanism here. Rather than documentation-only guidance ("we call them focus areas, not goals"), a schema can accept the team's terminology as valid types. A team that uses "outcome" instead of "goal", or "initiative" instead of "experiment", validates correctly without a custom schema fork.

    Combined with schema-level descriptive rules (#16), the schema can encode the team's working conventions — both terminology and qualitative expectations — in an inspectable, shareable form that tooling and agents can consume. The schema becomes the team's living definition of their planning model, not just a structural constraint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions