Documentation for the synthesis work system

Find the maintained instruction for the task in front of you. Setup, skill use, project records and verification have different questions to answer; follow the source that owns the behavior you need to understand.

Find an instruction

You need to…Open…
Choose components or an installation routeDownload and setup options, including the release evidence and requirements for the selected route.
Understand or choose a skillSynthesis skills and the source catalog.
Recover a project decisionProject management and the maintained project-record instructions.
Maintain current context and historyContext-lifecycle instructions.
Understand runtime support and its evidenceThe runtime integration contract.
Review an implementationImplementation-integrity instructions.
Report a reproducible problem or contributeContributing and support.

Read the state precisely

A file on disk establishes something different from an instruction loaded into a live client. A loaded instruction establishes something different from a successful task result.

For example, suppose you find a skill’s files but cannot establish whether the client selected it for a review. Report the files as present and selection as unknown. Inspect the review itself: did it quote the passage, examine its source and preserve the useful qualification? Do not infer selection from a fluent answer, or a good answer from the presence of a file.

The runtime integration contract describes the evidence required for each kind of check. Use current instructions for the component and client you actually have.

Bring evidence a maintainer can use

For a technical problem, record the relevant component and version, the action you attempted, what you expected and the actual result. Include enough permitted input to reproduce it. Say whether the observation came from source inspection, installed files or a live session.

Remove credentials and private material from a public report. The support policy directs security and disclosure concerns to maintainers privately and welcomes reproducible bug reports without promising a response time.

Rajiv Pant is the named author of the public system source. The repository’s governance, release history and license inventory remain the maintained references for changes to it.

Explore the complete system and its installation layers