Agent GIF - Sharing Intent

OK so my goal here is to keep the format clean… Gotta be honest, I don’t read specs much… Not sure that I will hit any appropriate standards but will attempt to vibe code my way through this on first attempt ^^.

My Phas Project is a multi-dimensional tree of panes.

The focus of the panes is that they are a ‘dimension’ so in that regard anything can be a pane ie a coding construct like a conditional, an image, audio, video, 3D, code, whatever… Panes are the contextual spine, they are views on the components of the contexts

Each nested pane represents an execution context (a.k.a. a code construct such as Output, Folder, Condition, Loop).

{
  “Name”: “”,
  “P”: [
  {
    “ID”: 1,
    “Type”: “Phout”,
    “PID”: “0”,
    “OID”: 0,
    “Name”: “Example”,
    “Code”: “{"Code":"return ‘Hello World’;","Message Response":"Hello World","AlwaysExecute":"1","Description":"Hello World"}”
  }
  ],
  “Forms”: null,
  “Data”: null,
  “Functions”: null,
  “CID”: “1”
}

Each pane is evaluated in the following way:
If pane is an output pane (‘Phout’) and:

  1. has a description (Intent) but No Code then this will be treated as a text pane or possible AI query
  2. has a description and code then this will be treated as code, in any language unless specified

Immediately we have a simple system where Chain Of Thought can be shared I think quite effectively as well as software ‘modules’, storyboards, game/project assets etc.

Next up we have Data… Every module here has it’s own data system, Named and Typed data

Data[*Name*]['Type'] = 'Table'; // Database / String / HTML
Data[*Name*]['Data'] = Appropriately formatted data array

Also included in the current spec is Forms and Functions…

Functions are GLOBAL to the GIF as is Data but each pane has it’s own scope equivalent to function scope.

Agent allows saving and sharing of complete process rather than just final results.

I want Agent GIF to be ‘Executable’, at least in a fuzzy sense.

Panes are designed to be iterated through (currently depth then width - though I’m interested in use cases for width then depth and also parallel threads).