> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useartifact.app/llms.txt
> Use this file to discover all available pages before exploring further.
# What I’m building toward
export const EssayDrawing = ({kind}) => {
const element = useRef(null);
const [visible, setVisible] = useState(false);
useEffect(() => {
if (typeof IntersectionObserver === 'undefined') {
setVisible(true);
return;
}
const observer = new IntersectionObserver(([entry]) => {
if (entry.isIntersecting) {
setVisible(true);
observer.disconnect();
}
}, {
threshold: 0.45
});
if (element.current) observer.observe(element.current);
return () => observer.disconnect();
}, []);
const descriptions = {
versions: 'Two onboarding designs are shown on the left: a three-field form above a newer one-field form. Only the three-field design is connected to the browser on the right, which still shows three fields. The new design does not change that connection or the implementation.',
feedback: 'Two paper studies fan apart. The earlier study has three outlined fields and an annotation clipped to its lower edge. The newer study has one field and no annotation. The annotation stays attached to the earlier study as the papers separate.'
};
return
{kind === 'versions' && }
{kind === 'feedback' &&
{}
}
;
};
A note from Nabil · September 5, 2026
**TL;DR**
I’m building Artifact to make it clear what a product change affects: the design, the implementation, the feedback, and the next piece of work. That understanding should carry between tools and agent sessions without constant upkeep. This describes the direction, not finished capabilities.
I’ve run into this with my own products: a design, a branch, and an agent session can each make sense on their own while their relationship becomes hard to follow. A shortcut in one session becomes an assumed requirement in the next. Over time, a product can move somewhere its owner never deliberately chose.
## One change, from design to feedback
Take an onboarding form with three fields. You explore a one-field design in Figma, but the browser still shows the original form.
Artifact should look for the actual choice in the material you choose to share, such as a review or an instruction to an agent. A newer frame doesn’t establish that you adopted it. If the choice was never recorded, that part needs your judgment.
Once you choose the one-field approach, Artifact should make the unfinished work clear: the implementation still needs updating and releasing.
After release, comments from people who used the three-field form still describe that earlier experience.
A complaint about asking for too much information may need a fresh test. A concern about trust could still apply. The redesign alone doesn’t establish that either problem was solved.
You should still be able to return to the original design or try a third approach. The record should help you reconsider a choice, including why it changed, rather than enforce it.
## Useful without becoming another job
Maintaining those connections has to be mostly the product’s responsibility. Asking you to label every file and classify every conversation would recreate the burden Artifact is meant to remove.
You should be able to follow a claim to its source, see where it depends on an inference, and correct a mistaken connection without rebuilding the whole picture.
A missing decision that blocks current work may deserve your attention. An unused draft can wait. Every interruption and correction has to count against the effort saved.
The value should show up during ordinary work: reviewing an implementation with its intended design beside it, or starting an agent session with the relevant constraints available in that tool, without a separate setup ritual.
***
If this sounds familiar, you can [join the Artifact waitlist](https://useartifact.app/beta).