🛠️Editorial Interface

The first version of this component is under active development.

Currently, our editorial process starts with either a submission to our intake form, or by someone creating an issue in GitHub. Then we have a manual four step process:

1. An Editor maps inputs to a Report datamodel and, then publishes it as a JSON file for review,

2. The Editor checks and edits report as needed, assigns taxonomy categories, then moves it to the database as reports/20XX/AVID-20XX-RXXXX.json,

3. The Editor may convert report to a new vuln or merge with an existing vuln, saved as vulnerabilities/20XX/AVID-20XX-VXXX.json (currently paused for new releases while AVID refines a working AI vulnerability definition),

4. Webmaster renders new reports and vulns to markdown files in the website source.

We plan to make this less manual over the course of the next few months by building an editorial UI and creating necessary integrations to enable developers push reports to AVID easily, and with more complete information upfront. Decision logs for each report will be logged in GitHub for openness and transparency.