@forwardimpact/schema 0.1.0

package/bin/fit-schema.js

@@ -0,0 +1,260 @@
+#!/usr/bin/env node
+
+/**
+ * fit-schema CLI
+ *
+ * Schema validation and index generation for Engineering Pathway data.
+ *
+ * Commands:
+ *   validate [--data=PATH]      Run full schema + referential validation
+ *   generate-index [--data=PATH] Generate _index.yaml files
+ *   validate:shacl              Validate SHACL schema syntax
+ *   --help                      Show help
+ */
+
+import { stat } from "fs/promises";
+import { join, resolve, dirname } from "path";
+import { fileURLToPath } from "url";
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+
+/**
+ * Parse CLI arguments
+ */
+function parseArgs(args) {
+  const command = args[0];
+  const options = {};
+
+  for (let i = 1; i < args.length; i++) {
+    const arg = args[i];
+    if (arg.startsWith("--data=")) {
+      options.dataDir = arg.slice(7);
+    } else if (arg === "--help" || arg === "-h") {
+      options.help = true;
+    } else if (arg.startsWith("--")) {
+      const [key, value] = arg.slice(2).split("=");
+      options[key] = value ?? true;
+    }
+  }
+
+  return { command, options };
+}
+
+/**
+ * Check if a directory exists
+ */
+async function dirExists(path) {
+  try {
+    const stats = await stat(path);
+    return stats.isDirectory();
+  } catch {
+    return false;
+  }
+}
+
+/**
+ * Find the data directory
+ */
+async function findDataDir(providedPath) {
+  if (providedPath) {
+    const resolved = resolve(providedPath);
+    if (await dirExists(resolved)) {
+      return resolved;
+    }
+    throw new Error(`Data directory not found: ${providedPath}`);
+  }
+
+  // Check common locations
+  const candidates = [
+    join(process.cwd(), "data"),
+    join(process.cwd(), "examples"),
+    join(__dirname, "../examples"),
+  ];
+
+  for (const candidate of candidates) {
+    if (await dirExists(candidate)) {
+      return candidate;
+    }
+  }
+
+  throw new Error(
+    "No data directory found. Use --data=PATH to specify location.",
+  );
+}
+
+/**
+ * Format validation results for display
+ */
+function formatValidationResults(result) {
+  const lines = [];
+
+  if (result.valid) {
+    lines.push("✅ Validation passed\n");
+  } else {
+    lines.push("❌ Validation failed\n");
+    lines.push("\nErrors:");
+    for (const error of result.errors) {
+      const path = error.path ? ` (${error.path})` : "";
+      lines.push(`  • ${error.type}: ${error.message}${path}`);
+    }
+  }
+
+  if (result.warnings?.length > 0) {
+    lines.push("\nWarnings:");
+    for (const warning of result.warnings) {
+      const path = warning.path ? ` (${warning.path})` : "";
+      lines.push(`  ⚠ ${warning.type}: ${warning.message}${path}`);
+    }
+  }
+
+  return lines.join("\n");
+}
+
+/**
+ * Validate command
+ */
+async function runValidate(dataDir) {
+  console.log(`🔍 Validating data in: ${dataDir}\n`);
+
+  const { runSchemaValidation, loadAllData } = await import("../lib/index.js");
+
+  // Load data first
+  const data = await loadAllData(dataDir, { validate: false });
+
+  // Run full validation
+  const result = await runSchemaValidation(dataDir, data);
+
+  console.log(formatValidationResults(result));
+
+  // Print summary
+  console.log("\n📊 Data Summary:");
+  console.log(`   Skills:      ${data.skills?.length || 0}`);
+  console.log(`   Behaviours:  ${data.behaviours?.length || 0}`);
+  console.log(`   Disciplines: ${data.disciplines?.length || 0}`);
+  console.log(`   Tracks:      ${data.tracks?.length || 0}`);
+  console.log(`   Grades:      ${data.grades?.length || 0}`);
+  console.log(`   Drivers:     ${data.drivers?.length || 0}`);
+
+  return result.valid ? 0 : 1;
+}
+
+/**
+ * Generate index command
+ */
+async function runGenerateIndex(dataDir) {
+  console.log(`📁 Generating index files in: ${dataDir}\n`);
+
+  const { generateAllIndexes } = await import("../lib/index.js");
+
+  const results = await generateAllIndexes(dataDir);
+
+  for (const [dir, files] of Object.entries(results)) {
+    if (files.error) {
+      console.log(`❌ ${dir}/_index.yaml: ${files.error}`);
+    } else {
+      console.log(`✅ ${dir}/_index.yaml (${files.length} files)`);
+    }
+  }
+
+  return 0;
+}
+
+/**
+ * SHACL validation command
+ */
+async function runValidateShacl() {
+  console.log("🔍 Validating SHACL schema syntax...\n");
+
+  const schemaPath = join(__dirname, "../schema/rdf/pathway.ttl");
+
+  try {
+    const { default: N3 } = await import("n3");
+    const { readFile } = await import("fs/promises");
+
+    const turtleContent = await readFile(schemaPath, "utf-8");
+    const parser = new N3.Parser({ format: "text/turtle" });
+
+    const quads = [];
+    parser.parse(turtleContent, (error, quad) => {
+      if (error) throw error;
+      if (quad) quads.push(quad);
+    });
+
+    console.log(`✅ SHACL syntax valid (${quads.length} triples)\n`);
+    return 0;
+  } catch (error) {
+    console.error(`❌ SHACL syntax error: ${error.message}\n`);
+    return 1;
+  }
+}
+
+/**
+ * Show help
+ */
+function showHelp() {
+  console.log(`
+fit-schema - Schema validation for Engineering Pathway
+
+Usage:
+  fit-schema <command> [options]
+
+Commands:
+  validate           Run full schema + referential validation
+  generate-index     Generate _index.yaml files for directories
+  validate:shacl     Validate SHACL schema syntax
+
+Options:
+  --data=PATH        Path to data directory (default: ./data or ./examples)
+  --help, -h         Show this help message
+
+Examples:
+  fit-schema validate
+  fit-schema validate --data=./my-data
+  fit-schema generate-index
+  fit-schema validate:shacl
+`);
+}
+
+/**
+ * Main entry point
+ */
+async function main() {
+  const { command, options } = parseArgs(process.argv.slice(2));
+
+  if (options.help || !command) {
+    showHelp();
+    process.exit(command ? 0 : 1);
+  }
+
+  try {
+    let exitCode = 0;
+
+    switch (command) {
+      case "validate": {
+        const dataDir = await findDataDir(options.dataDir);
+        exitCode = await runValidate(dataDir);
+        break;
+      }
+      case "generate-index": {
+        const dataDir = await findDataDir(options.dataDir);
+        exitCode = await runGenerateIndex(dataDir);
+        break;
+      }
+      case "validate:shacl":
+        exitCode = await runValidateShacl();
+        break;
+      default:
+        console.error(`Unknown command: ${command}`);
+        showHelp();
+        exitCode = 1;
+    }
+
+    process.exit(exitCode);
+  } catch (error) {
+    console.error(`Error: ${error.message}`);
+    process.exit(1);
+  }
+}
+
+main();

package/examples/behaviours/_index.yaml

@@ -0,0 +1,8 @@
+# Auto-generated index for browser loading
+# Do not edit manually - regenerate with: npx pathway --generate-index
+files:
+  - outcome_ownership
+  - polymathic_knowledge
+  - precise_communication
+  - relentless_curiosity
+  - systems_thinking

package/examples/behaviours/outcome_ownership.yaml

@@ -0,0 +1,43 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/behaviour.schema.json
+
+name: Own the Outcome
+human:
+  description:
+    Business outcomes trump engineering elegance. Embrace extreme ownership of
+    what you build—not just code quality, but business relationships, impact
+    metrics, and end-to-end results. Accept technical debt when it enables
+    faster business value, but own the consequences. AI may generate the code,
+    but responsibility for outcomes remains with you.
+  maturityDescriptions:
+    emerging:
+      Takes responsibility for assigned tasks with supervision; follows through
+      when reminded; asks for help appropriately; understands that work serves
+      business goals
+    developing:
+      Owns task completion independently; reviews AI-generated code critically;
+      makes pragmatic trade-offs between speed and polish; takes responsibility
+      for understanding code before shipping; considers business impact of
+      technical decisions
+    practicing:
+      Takes end-to-end ownership of features and business outcomes; accepts
+      technical debt intentionally when it accelerates value; builds trust
+      through rapid delivery of working solutions; owns stakeholder
+      relationships; balances quality with delivery speed
+    role_modeling:
+      Drives accountability culture focused on outcomes not deliverables; owns
+      business relationships and impact metrics across their function; makes
+      trade-offs between custom solutions and generalizable work; there is no "I
+      must run this by X"; ensures verification rigor for AI-generated code
+    exemplifying:
+      Defines organizational accountability standards focused on business
+      impact; shapes industry practices around outcome ownership in the AI era;
+      sponsors transformational initiatives with full outcome accountability;
+      recognized externally for ownership culture leadership
+
+agent:
+  title: Own the outcome end-to-end
+  workingStyle: |
+    At each step:
+    1. Define success criteria before starting
+    2. Verify the change achieves the criteria
+    3. Don't hand off until you've validated the work

package/examples/behaviours/polymathic_knowledge.yaml

@@ -0,0 +1,41 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/behaviour.schema.json
+
+name: Be Polymath Oriented
+human:
+  description:
+    Depth of expertise combined with breadth across multiple domains. Go beyond
+    T-shaped, building knowledge that spans technology, business, science, and
+    the pharmaceutical domain. Like Jim Gray, who made better architectural
+    decisions by understanding business beyond his database expertise, see
+    connections others miss.
+  maturityDescriptions:
+    emerging:
+      Recognizes that problems benefit from cross-disciplinary insights; shows
+      interest in domains beyond immediate technical requirements
+    developing:
+      Applies knowledge from one domain to inform decisions in another; studies
+      adjacent fields like design, business, or science; begins learning domain
+      language of business partners
+    practicing:
+      Bridges gaps between engineering, design, business, and science; rapidly
+      immerses in new domains; speaks the language of Commercial, Manufacturing,
+      or R&D; makes better decisions by understanding broader context
+    role_modeling:
+      Champions cross-disciplinary learning; creates holistic solutions spanning
+      technical and business domains; embodies the Renaissance Engineer ideal;
+      translates specialized knowledge into accessible explanations; thinks like
+      a business insider
+    exemplifying:
+      Shapes organizational learning strategy across disciplines; recognized
+      industry thought leader bridging technology and business; advises
+      executive leadership on cross-functional strategy; publishes on polymathic
+      approaches to engineering; influences industry hiring and development
+      practices
+
+agent:
+  title: Apply cross-domain insight
+  workingStyle: |
+    When solving problems:
+    1. Draw on knowledge from multiple domains
+    2. Consider perspectives beyond pure technical implementation
+    3. Look for patterns that can be generalized

package/examples/behaviours/precise_communication.yaml

@@ -0,0 +1,39 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/behaviour.schema.json
+
+name: Communicate with Precision
+human:
+  description:
+    In the age of AI, clarity becomes a superpower. Communicate with
+    precision—reducing ambiguity in specifications, requirements, and designs.
+    Natural language is inherently vague; AI can only generate accurate
+    solutions when given clear, unambiguous intent.
+  maturityDescriptions:
+    emerging:
+      Communicates basic technical concepts when prompted; participates in team
+      discussions; writes simple documentation
+    developing:
+      Writes clear documentation and specifications; reduces ambiguity in
+      requirements; crafts effective prompts for AI tools; adapts communication
+      style for different audiences
+    practicing:
+      Separates requirements, designs, and tasks with precision; enables AI to
+      generate accurate code through clear specifications; translates between
+      technical and business language; facilitates productive discussions
+    role_modeling:
+      Creates spec-driven development practices; mentors others on precise
+      communication; spans C-level executives to frontline workers; drives
+      clarity as a core value across their function; represents the organization
+      externally
+    exemplifying:
+      Shapes industry standards for technical communication; recognized
+      authority on spec-driven AI development; influences organizational
+      communication culture; publishes on precision in the AI era; keynotes at
+      industry conferences
+
+agent:
+  title: Communicate with clarity
+  workingStyle: |
+    When providing output:
+    1. Separate blocking issues from suggestions
+    2. Explain the "why" behind each recommendation
+    3. Provide concrete examples or alternatives

package/examples/behaviours/relentless_curiosity.yaml

@@ -0,0 +1,37 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/behaviour.schema.json
+
+name: Don't Lose Your Curiosity
+human:
+  description:
+    The driving force behind learning and invention. Protect your instinct to
+    break things down and understand them deeply. Embrace an experimental spirit
+    that treats failure as a path to discovery, not a setback to avoid.
+  maturityDescriptions:
+    emerging:
+      Asks basic questions when prompted; shows interest in learning about
+      immediate tasks; willing to try new approaches
+    developing:
+      Regularly asks clarifying questions about "why" and "how"; explores
+      related topics with guidance; experiments without fear of failure;
+      investigates how AI tools work rather than using them blindly
+    practicing:
+      Proactively investigates root causes; experiments with new technologies
+      and AI capabilities; protects time for exploration; treats failure as
+      learning; discovers requirements through immersion in problem spaces
+    role_modeling:
+      Drives team curiosity through challenging questions; creates environments
+      where exploration and experimentation are encouraged; models problem
+      discovery orientation; seeks out ambiguity rather than avoiding it
+    exemplifying:
+      Shapes organizational culture around curiosity and continuous learning;
+      sponsors experimental initiatives across the organization; recognized
+      externally as a thought leader in problem discovery; influences industry
+      practices around innovation and exploration
+
+agent:
+  title: Investigate before acting
+  workingStyle: |
+    Before taking action:
+    1. Confirm your understanding of the goal
+    2. Identify unknowns that could affect the approach
+    3. Research unfamiliar areas via subagent if needed

package/examples/behaviours/systems_thinking.yaml

@@ -0,0 +1,40 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/behaviour.schema.json
+
+name: Think in Systems
+human:
+  description:
+    The ability to see beyond individual components to understand how the entire
+    system behaves. Like understanding how reintroducing wolves to Yellowstone
+    transformed not just deer but rivers, engineers recognize that every
+    service, API, and queue is part of a larger whole—isolated changes ripple
+    across the system.
+  maturityDescriptions:
+    emerging:
+      Recognizes that systems have interconnected parts; considers immediate
+      dependencies in code; understands basic cause-and-effect
+    developing:
+      Identifies upstream and downstream impacts; uses observability tools to
+      trace requests across services; understands feedback loops; maps
+      dependencies before making changes
+    practicing:
+      Maps complex system interactions across technical and business domains;
+      anticipates cascading effects; designs systems that degrade gracefully;
+      understands how technology changes impact business operations
+    role_modeling:
+      Shapes systems design practices across their function; conducts chaos
+      engineering experiments; influences cross-team architecture decisions;
+      creates clarity from complexity; bridges technical systems with business
+      processes
+    exemplifying:
+      Defines organizational systems architecture principles; recognized
+      industry authority on complex systems; advises executive leadership on
+      systemic risks and opportunities; publishes thought leadership on systems
+      thinking in technology organizations
+
+agent:
+  title: Consider the whole system
+  workingStyle: |
+    For every change:
+    1. Identify upstream and downstream impacts
+    2. Consider non-functional requirements (performance, security)
+    3. Document assumptions and trade-offs

package/examples/capabilities/_index.yaml

@@ -0,0 +1,8 @@
+# Auto-generated index for browser loading
+# Do not edit manually - regenerate with: npx pathway --generate-index
+files:
+  - business
+  - delivery
+  - people
+  - reliability
+  - scale

package/examples/capabilities/business.yaml

@@ -0,0 +1,189 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/capability.schema.json
+
+name: Business
+emojiIcon: 💼
+displayOrder: 8
+description: |
+  Understanding and driving business value.
+  Includes domain knowledge, stakeholder management, strategic thinking,
+  and translating between technical and business contexts.
+professionalResponsibilities:
+  awareness:
+    Understand the business context for your assigned work and communicate
+    progress clearly when asked
+  foundational:
+    Connect your technical work to business outcomes, engage with stakeholders
+    to clarify requirements
+  working:
+    Translate business needs into technical solutions, manage stakeholder
+    expectations, and articulate technical decisions in business terms
+  practitioner:
+    Drive business outcomes through technical solutions across your area,
+    influence product roadmaps, and partner effectively with business
+    stakeholders
+  expert:
+    Shape technology-driven business strategy, represent technical perspective
+    at executive level, and be recognized as a bridge between engineering and
+    business
+managementResponsibilities:
+  awareness:
+    Understand business context and communicate team progress to stakeholders
+    with guidance
+  foundational:
+    Align team priorities with business objectives, manage stakeholder
+    relationships, and communicate team impact
+  working:
+    Translate business strategy into team objectives, own stakeholder
+    relationships, and ensure team delivers business value
+  practitioner:
+    Partner with business leaders to shape strategy for your area, influence
+    direction across teams, and deliver measurable business impact
+  expert:
+    Shape technology-driven business strategy, represent engineering at
+    executive level, and own strategic business outcomes
+skills:
+  - id: stakeholder_management
+    name: Stakeholder Management
+    isHumanOnly: true
+    human:
+      description:
+        Building relationships with and managing expectations of stakeholders
+        across the organization, from frontline workers to C-level executives
+      levelDescriptions:
+        awareness:
+          You identify key stakeholders for your work and communicate status
+          when asked. You understand that different stakeholders have different
+          needs.
+        foundational:
+          You proactively update stakeholders on progress, handle basic
+          expectation setting, and escalate concerns appropriately. You build
+          rapport with regular collaborators.
+        working:
+          You manage multiple stakeholders with different interests, navigate
+          conflicting priorities diplomatically, and build trust through
+          consistent delivery. You tailor communication to each audience.
+        practitioner:
+          You influence senior stakeholders effectively across your area, manage
+          complex stakeholder landscapes with competing agendas, build trust
+          rapidly with new stakeholders, and shield teams from organizational
+          friction.
+        expert:
+          You shape stakeholder practices across the business unit. You manage
+          executive relationships, represent engineering at the highest levels,
+          and are recognized for exceptional stakeholder partnerships.
+  - id: technical_writing
+    name: Technical Writing
+    human:
+      description:
+        Creating clear, accurate, and useful technical documentation. Good specs
+        enable AI to generate accurate solutions; poor specs lead to poor
+        results.
+      levelDescriptions:
+        awareness:
+          You document your own work following team templates and standards. You
+          keep code comments current and write basic README content.
+        foundational:
+          You write clear READMEs, inline documentation, and technical guides.
+          You update existing docs when making changes and ensure documentation
+          matches implementation.
+        working:
+          You create comprehensive documentation for complex systems. You write
+          precise specifications that enable accurate AI-generated code,
+          establish documentation practices for your projects, and ensure docs
+          are discoverable.
+        practitioner:
+          You define documentation standards across teams in your area, create
+          documentation systems and templates, train engineers on spec-driven
+          development, and ensure documentation quality across projects.
+        expert:
+          You shape documentation culture and standards across the business
+          unit. You innovate on documentation approaches, are recognized for
+          exceptional technical writing clarity, and lead documentation
+          initiatives.
+    agent:
+      name: technical-writing
+      description: Guide for creating clear technical documentation.
+      useWhen: |
+        Writing READMEs, API docs, specifications, or any technical content
+        that needs to be clear and accurate.
+      stages:
+        specify:
+          focus: |
+            Define documentation requirements and audience needs.
+            Clarify what the documentation must accomplish.
+          activities:
+            - Identify target audience and their skill level
+            - Document what questions the docs must answer
+            - Define documentation type (README, API, spec, tutorial)
+            - Specify accuracy and completeness requirements
+            - Mark ambiguities with [NEEDS CLARIFICATION]
+          ready:
+            - Audience is identified
+            - Questions to answer are documented
+            - Documentation type is chosen
+            - Requirements are clear
+        plan:
+          focus: Understanding audience and planning documentation
+          activities:
+            - Identify target audience and their needs
+            - Determine document type and structure
+            - List prerequisites and assumptions
+            - Outline key sections and content
+          ready:
+            - Audience is identified
+            - Document type and structure planned
+            - Prerequisites listed
+            - Outline complete
+        code:
+          focus: Writing clear and accurate documentation
+          activities:
+            - Write using simple, direct language
+            - Structure content for scanning
+            - Include tested, runnable examples
+            - Define technical terms
+          ready:
+            - Purpose clear in first paragraph
+            - Examples are tested and work
+            - Technical terms are defined
+            - Structure supports scanning
+        review:
+          focus: Verifying documentation quality
+          activities:
+            - Check accuracy against implementation
+            - Verify examples are runnable
+            - Review for clarity and completeness
+            - Test with target audience if possible
+          ready:
+            - Documentation matches implementation
+            - All examples verified working
+            - No ambiguous pronouns
+            - Structure is logical and complete
+        deploy:
+          focus: |
+            Publish documentation and ensure it reaches the audience.
+            Set up maintenance process.
+          activities:
+            - Publish to documentation site
+            - Announce to relevant teams
+            - Add to search indexes and navigation
+            - Establish update and review schedule
+          ready:
+            - Documentation is published and accessible
+            - Audience can discover and find it
+            - Search and navigation are updated
+            - Maintenance schedule is established
+    implementationReference: |
+      ## Document Types
+
+      | Type | Purpose | Key Sections |
+      |------|---------|--------------|
+      | README | Project overview | Description, Getting Started, Usage |
+      | API Docs | API reference | Endpoints, Parameters, Examples |
+      | Spec | Design proposal | Problem, Solution, Alternatives |
+      | Tutorial | Learning guide | Objective, Steps, Outcomes |
+
+      ## Writing Principles
+      - Use simple, direct language
+      - One idea per sentence
+      - Active voice over passive
+      - Lead with most important info