Brief for AI agent

Ends

Build robust WBS for projects using reason about both the end state, and the processes to achieve the end state. Do this by using both domain ontologies, and a foundation ontology of your choice. This should achieve a WBS that is explainable. Do this for the project scenarios given by the user or for those listed below. Each time, compare this with a WBS constructed via a problem and domain file in PDDL for that scenario, and state which is better and why. After each key step, present and check with the user that she wants you to continue with the next step.

Ways

  1. High level ontology. your choice eg. BFO
  2. Mid level ontology for mapping the enterprise and project (optional), if 1 and 3 do the job well enough. eg. would be the gist ontology for enterprise and a project ontology of your choice
  3. Domain ontology. An example would be the Digital Construction ontology.
  4. You will need to name your own domain to encode any special , local arrangements, as well as details of the instances.

Means

write a single html file with interactive features to model and capture and explain and illustrate your results, compliant with the attached canvas guidelines for how you write the html.

Project scenarios

  1. a tunnel under the Solway Firth

Guidelines

if I just say lets go, what I mean is, lets go forward towards the expressed ends, via the most feasible ways expressed, using the means available, in the full context of the instructions and documents.

Back to app index