What provenance should an enterprise AI dataset include?
Connect source, selection, preparation and version records with the separate authority needed for the proposed dataset use.
7 min read
Editorial date
Read the history behind software work
A current repository and a history of decisions describe different aspects of engineering work. Use these guides to examine provenance, workflow context and what a source company can substantiate before any records are shared.
Guides on engineering histories
7 guides
What does a Git and pull request export actually preserve?
Check whether exported commits, reviews and checks retain the version relationships needed to understand an engineering task.
6 min read
Editorial date
Where can you investigate licensing a codebase and its engineering history?
Match a code snapshot, engineering history or executable task to the relevant route and its actual evidence request.
5 min read
Editorial date
How to assess a software repository for agent training
Trace issue context, revisions, review and tests to assess whether repository history supports a reproducible agent task.
5 min read
Editorial date
Can one company license code history and support data separately?
Map shared records and rights before treating engineering history and support investigations as separate licensing opportunities.
6 min read
Editorial date
Can you license a private GitHub repository with third-party code?
Review contributions, licenses, fixtures and history against the exact repository material and AI uses being proposed.
6 min read
Editorial date
How a software startup can choose a data-licensing partner
Match a startup’s retained records, contribution rights and team capacity to the actual role a licensing partner would perform.
6 min read
Editorial date