Skip to content

Delta Engineering Plan: OSSA Capabilities

This plan defines the engineering investigations required to prove the remaining delta for OSSA capabilities. It does not authorize code changes.

1. Manifest Validation

  • Current State: PHP implementation
  • Desired State: Reference implementation (NPM OpenStandardAgents)
  • Unknown: How does the Drupal runtime invoke the reference implementation securely and performantly?
  • Investigation Required: YES
  • Engineering Tasks:
    • Investigate feasibility of a local Node.js child process vs a decoupled validation microservice.
    • Determine if validation can be shifted entirely offline into CI/CD pipelines.

2. Discovery Transport

  • Current State: Custom REST controller
  • Desired State: Core transport (JSON:API)
  • Unknown: Does JSON:API natively support the required .well-known discovery schema formats without excessive customization?
  • Investigation Required: YES
  • Engineering Tasks:
    • Audit JSON:API feature parity against current discovery responses.
    • Determine what Normalizer extensions are required to hit the spec if parity fails.

3. Registry UI (Catalog)

  • Current State: Custom controller
  • Desired State: Views
  • Unknown: Can Views support all required administrative behaviors (inline validation, quick-launch execution)?
  • Investigation Required: YES
  • Engineering Tasks:
    • Prototype a View against the ossa_agent entity type to test filtering and batch operations.
    • Determine how to trigger arbitrary execution routes from a Views row.

4. Tool Binding

  • Current State: Custom mapping logic
  • Desired State: Tool API (drupal/tool) extension
  • Unknown: Are the metadata models of OSSA Tools perfectly compatible with Drupal Tool API Plugins?
  • Investigation Required: YES
  • Engineering Tasks:
    • Map OSSA tool parameters to Drupal Plugin definition structures.
    • Identify any data loss in bidirectional conversion.

5. Async Execution

  • Current State: Symfony Messenger
  • Desired State: Symfony Messenger / ECA
  • Unknown: Does the current implementation conflict with generalized ECA workflow models?
  • Investigation Required: NO (Currently aligned, monitor for overlap during ECA integration).