Product validation · No software available yet
Help shape a governed AI engineering team for the tools your company already approves.
Edukas Solutions is researching a configurable operating layer for GitHub Copilot in VS Code. The concept would define engineering roles, repeatable workflows, human approval points, and optional Heartwood memory. There is no downloadable Heartwood Copilot pack, runtime, or supported production UI today.
This page is for research, not a software sale. Edukas Solutions is independent and is not affiliated with Microsoft or GitHub.
Does your AI-assisted engineering workflow depend on one person’s prompt craft?
We want to learn how software teams standardize planning, research, architecture, implementation, and verification when AI use must stay inside approved developer tools.
If every project starts by restating the same constraints—or if one agent plans, implements, and reviews its own work—tell us where the process becomes difficult to trust, repeat, or govern.
Questions we are testing
Would a maintained team method be more useful than another prompt folder?
The following are product hypotheses, not available capabilities.
Clear roles
Would named responsibilities for planning, research, architecture, implementation, and verification make work easier to review?
Human decision points
Which actions should always stop for an identifiable human—merges, deployments, external writes, destructive changes, or policy changes?
Governed continuity
Would optional Heartwood memory help if approved context could carry forward with policy and source information, rather than replaying unfiltered chat history?
Administrator review
What would an administrator need to inspect before approving configuration for a team: files, tools, permissions, data locations, network behavior, update policy, or evidence?
Collaboration boundary
Would requests and approvals in Microsoft Teams be useful if coding stayed in the approved IDE? Teams is a planned research direction only; there is no Heartwood Copilot Teams app or gateway today.
Bring one workflow your team repeats.
This research is intended for teams that:
- use or are evaluating GitHub Copilot in VS Code;
- have a recurring engineering workflow that is difficult to standardize;
- need human review or administrator control around AI-assisted work; and
- can describe what evidence would make a pilot trustworthy.
Tell us about the workflow, the people who approve it, and the boundary that matters most. A submission is an expression of interest, not a software order or promise of access.
Honest status
Product definition first. Clean-room implementation next.
Heartwood Copilot is currently in product definition and design-partner validation. Its repository contains strategy, product, architecture, pricing, positioning, and execution documents needed to begin a clean-room implementation.
There is no distributable runtime, supported production UI, shipped Skills Pack, signed release manifest, public evaluation result, or customer case study for this product today. We will not publish persona or skill counts until a signed release manifest can support them.
What we are validating now: the buyer, the first workflow, the approval boundary, the initial GitHub Copilot/VS Code target, and whether governed memory belongs in the first useful version.
The conversation starts with your constraints.
- Which engineering workflow do you repeat often enough to standardize?
- Where does a single general AI assistant create self-review or context problems?
- Which actions require human approval in your organization?
- What may be installed on a managed developer workstation?
- What source, memory, and evidence boundaries would an administrator require?
- What result would make a controlled pilot worth continuing?
Frequently asked
No. There is no downloadable pack, runtime, supported production UI, or shipped release today.
No. Edukas Solutions is an independent company. GitHub Copilot, GitHub, Microsoft, Visual Studio Code, and related marks belong to their respective owners.
No public count is proposed at this stage. Any future count must come from the signed manifest of the release being offered.
No Heartwood Copilot adapter or Teams app is available today. GitHub Copilot in VS Code is the first intended validation target. Other coding hosts and a Teams collaboration surface remain research directions unless and until they are implemented, tested, and released.
Not in any Heartwood Copilot release today, because no Heartwood Copilot release exists. Optional Heartwood integration is part of the product direction and must be validated against an explicit deployment, license, and security boundary before it can be offered.
No. This validation page has no checkout. It invites research participation only. The separate existing Skills Pack pre-order on the founding page is not redefined by this page.
Edukas Solutions may use the submission to assess research fit and may invite selected teams to a conversation. A submission does not guarantee a pilot, product access, release date, price, or commercial terms.
Before we build the pack, help us define the workflow worth packaging.
Show us the engineering process your team repeats, the decisions a human must own, and the evidence your administrator would need to trust a controlled pilot.