Repository navigation
Added: Seed bounded AI-authored tool lifecycle - #17
Draft
tjXJNOOBIE wants to merge 2 commits into
Draft
tjXJNOOBIE wants to merge 2 commits into
tjXJNOOBIE wants to merge 2 commits into
Conversation
Reason: - Promote TJ-215 into a durable Function Catalog engineering lane. Changes: - Added the generated-tool proposal, independent review, registration, quarantine, rollback, and regression lifecycle design. Validation: - Inspected current Function Catalog workflow and agent/catalog runtime architecture on `staging/platform`. - Not run: implementation, Java 25, sandbox, registration, or publication validation.
This was referenced Aug 16, 2026
Reason: - Remove traffic-light and generic failure-first semantics from an engineering design. - Preserve the existing catalog, runtime, sandbox, and authority boundaries. Changes: - Replaced YELLOW open edges with named unresolved architecture decisions. - Made planned lifecycle implementation and matching validation one coherent boundary. - Clarified that the design document is not implementation or publication authorization. Validation: - Reviewed the PR's current Function Catalog/runtime architecture boundaries and staging lineage. - Documentation-only correction; no candidate execution or runtime validation run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
TJ-215 is a Draft Function Catalog engineering lane beneath persistent Platform Staging #10 for a bounded AI-authored capability lifecycle: proposal, generated candidate, isolated build/test/review, versioned registration or quarantine, bounded publication, regression surveillance, and rollback/retirement. Generated tools never grant themselves authority.
Relationship
TJ-215 -> Function Catalog Platform Staging #10 -> main promotion -> separately authorized deployment/publicationThe design reuses
AIFunctionCatalogView, provider-neutralAIAgentRuntime, runtime budgets/revocation, and Tavall Cloud development-only execution placement instead of creating a second capability/authority plane.Current engineering state
Current exact head:
1148c7b8ad4238e792309a19d2b95fd9ff1c2535.State:
PLANNED_IMPLEMENTATION_NEEDS_CURRENT_REGISTRATION_AND_RUNTIME_CHARACTERIZATION.This head contains the corrected architecture/design objective only. No generated capability implementation or execution is claimed.
Template/language, sandbox-image, signing/versioning, promotion, protected-data, integration-environment, graduation-policy, and UX questions remain named decisions rather than engineering lifecycle state.
Architecture boundaries
AIFunctionCatalogViewremains the publication/discovery constraint rather than a second MCP-only authority;Engineering / testing discipline
Characterize current registration/view/provider/runtime/versioning/sandbox seams first. Then implement the smallest typed lifecycle + evidence + quarantine boundary with matching behavior/integration coverage. Existing registered tools can become regression fixtures. Testing validates behavior but does not prescribe whether coverage or production implementation is authored first, and no intermediate test state is an engineering lifecycle gate.
Validation truth
Current Function Catalog/runtime architecture and staging lineage were inspected. No exact-head Java 25, candidate execution, sandbox run, registration, MCP publication, or runtime acceptance is claimed.
Next action
Characterize current registration/view/provider seams, then implement typed proposal/package/lifecycle/evidence contracts plus versioned registration/quarantine behavior and matching tests. Add sandbox/publication integration only through existing authority boundaries.
Keep Draft. No generated-code execution, catalog registration, publication, staging fan-in,
mainpromotion, release, or deployment is authorized.Refs TJ-215
State: PLANNED_IMPLEMENTATION_NEEDS_CURRENT_REGISTRATION_AND_RUNTIME_CHARACTERIZATION
Owner: TJ
Parent: #10
ExactHead: 1148c7b
Validation: SOURCE_POLICY_REPAIRED; IMPLEMENTATION_PENDING; RUNTIME_VALIDATION_PENDING
Next Action: characterize current catalog/runtime seams, implement the real typed lifecycle/evidence/quarantine boundary with matching tests, then validate candidate sandbox/publication behavior.