Issue Description
We no longer have a strong opinion on the form of a manifest. Any agent runtime should operate over SLIM, and that runtime can be capture in the agent record using OASF + Agent Directory.
Prposed Solution
Suggest to remove the Manifest heading in the navigation panel, and the content there, and make it clear in OASF/Dir as to how to capture agent runtime information AND the any manifest information in the directory record; and also make it clear in SLIM that any runtime can be supported.
OASF & Directory should list the Directory use cases also: (1) publish & discover for agentic developers, (2) composition of agentic systems at runtime (a system should be able to connect to directory to find the right resources and then have all information needed to utilize those resources)
Affected Component
CSIT
Checklist
Issue Description
We no longer have a strong opinion on the form of a manifest. Any agent runtime should operate over SLIM, and that runtime can be capture in the agent record using OASF + Agent Directory.
Prposed Solution
Suggest to remove the
Manifestheading in the navigation panel, and the content there, and make it clear in OASF/Dir as to how to capture agent runtime information AND the any manifest information in the directory record; and also make it clear in SLIM that any runtime can be supported.OASF & Directory should list the Directory use cases also: (1) publish & discover for agentic developers, (2) composition of agentic systems at runtime (a system should be able to connect to directory to find the right resources and then have all information needed to utilize those resources)
Affected Component
CSIT
Checklist