Use your notes to give AI a useful project assignment

Start with a project already in your vault. Work out what contribution would help, give it relevant context, and review what comes back before it becomes direction for the project.

The full method is Smart Loop: Clarify → Delegate → Compound. Clarify what the work needs. Delegate a contribution you can judge. Compound by retaining useful work or learning so the next pass starts better informed—or the completed result is ready to use.

You do not need to reorganize your entire vault or install the whole suite to understand the method.

1. Recover the project before expanding the request

Choose the project note and sources that actually matter to the next decision.

Smart Connections can surface candidates. Inspect them before treating them as current direction: a related note may be historical, exploratory, or useful for a different question.

When you have a supported connected route, this is one way to ask for an initial read-only contribution:

Read [project note] and [relevant reference notes].

From those sources, summarize:
- the intended outcome;
- the current decisions and constraints relevant to the next work;
- one useful next contribution, and how I could judge it.

Cite the supporting notes. Distinguish what is explicit from what you
infer, and identify missing information rather than filling it in.

Return the brief in chat. Do not edit notes or create proposals yet.

This is a suggested assignment, not a tested command or a security control.

Check the result against the sources. You are trying to reach a useful request—not automatically accept AI's account of your project.

For a read-through without connected tools, the same questions can guide your own comparison.

2. Choose the judgment the next contribution should support

An outline, comparison, draft section, or proposed correction may each be an appropriate contribution. Choose what advances the work and what you can reasonably review.

The correction workflow below fits when a source supports changing a specific existing passage. It is not a requirement to find something wrong with every note.

A real example: the instruction directing this funnel

One passage in my marketing notes said:

This is the umbrella that makes every plugin feel necessary without making the suite feel bloated.

That instructed later work to make the suite seem necessary. For this funnel, the more useful direction was to explain which contributions served the reader's work.

The product-role reference said each part had “one dominant job.” It supported reconsidering the instruction, but it did not dictate the correct replacement.

A proposal offered:

This umbrella makes each plugin's contribution and handoffs understandable, so people can use the parts that serve their work without treating the whole suite as a prerequisite.

Creating the explicit proposal left the source unchanged. I accepted the correction, and the replacement was saved in the marketing note.

The next funnel outline then had a useful constraint: explain complementary product roles without making the whole suite a prerequisite.

This is the business result established by the record: a reviewed instruction and its use in planning. It does not establish increased sales.

3. Request one supported change for review

The connected exercise requires an available Connect Pro correction-proposal route. Check the supported setup and access instructions for your client.

Before a write-related task, use a read-only action on one short note you are comfortable sharing. Verify its identity and returned text against Obsidian. A connected indicator is not the same as a correct read.

Access and review are different boundaries. Smart Inbox handles explicit proposal actions, not unrelated direct writes. Task wording does not replace permissions, and note content may reach the chosen provider according to the actual client and tool configuration.

For a specific passage with relevant evidence, adapt this request:

Compare [target note and passage] with [reference note or section]
for [the project decision].

Read both sources. Explain whether the reference should govern
this particular passage, including any difference in scope.

If it supports one material correction, use the explicit
correction-proposal action to queue it for Smart Inbox review.
Include the exact target, proposed replacement, supporting excerpt,
and reason.

Do not directly edit the source. If the evidence is insufficient
or the proposal action is unavailable, explain the gap and stop
without writing.

This is a suggested request, not the historical prompt from the case. Do not substitute a direct-write action for this exercise.

4. Make the review decision and inspect the result

Read the reference, target, replacement, and reason together.

Does the source support the change in this note? Does the replacement preserve the meaning you intend? What would the next assignment do differently if you accepted it?

The exact replacement deserves more attention than the confidence of its rationale.

For the Connect Pro 2.0.3 review flow:

1. Select the pending correction in Smart Inbox. Inspect the original passage, source evidence, and proposed replacement.
2. Edit the permitted replacement if needed. Done editing retains the review draft; it does not apply the change. Inspect the updated preview.
3. Use Apply correction, inspect the final confirmation, and confirm only the change you intend. Cancel returns to pending review without applying.
4. Alternatively, use Reject to record a rejection without changing the source. Leaving the item pending is a different state.
5. After application, read the affected note and check the saved passage and surrounding meaning. The record of a decision is not a substitute for inspecting the result.

Use documentation appropriate to your installed version if the controls differ. If a source changes, re-read it and inspect a current preview. Stop on a partial-application or recovery warning rather than blindly repeating the operation.

Rejecting can be the right decision, but it has not delivered the proposed correction. Identify what still needs evidence, a different contribution, or no change at all.

5. Let the decision improve what follows

Review checks the result. Compound changes the next starting point.

For the marketing case, the accepted direction can now guide a landing-page assignment: explain which product contribution helps the work, without presenting the whole suite as compulsory.

That is the useful continuation. It need not be another round of editing the same sentence.

Keep accepted direction distinguishable from previous drafts and unreviewed suggestions. Retain a useful deliverable when the work is complete; retain a clarification when the attempt reveals something missing.

Maintained named Smart Contexts help reuse relevant selections and rules. Check what resolves for the present assignment because the underlying sources can change.

Smart Chat can attach a provider thread to the project note, giving you a route back to that conversation. This does not mean Core owns its complete transcript or that the conversation is always current authority.

Relevant proposal feedback may help explain earlier decisions. It is a record to consult, not automatic preference learning.

When a visual view helps

If a source set is easier to recognize visually, Smart Graph Pro can help you inspect a region, refine the selection, and hand it to Context. Standalone Graph Pro is distinct from graph displays inside Smart Connections.

This is an optional preparation route. The record does not establish that Connections or Graph discovered the historical marketing mismatch.

6. Give the capability a genuine next job

Choose another contribution because the project needs it—not to create an appearance of repeated use.

A changed scope, a revised product decision, or new reference material may justify examining a note again. The comparison may also confirm that the existing wording should stay.

For example, a project plan may need checking against a changed brief. The manual route is to compare the notes and make any warranted edit yourself. With Connect Pro, you can ask AI to inspect the notes and queue an exact correction with supporting evidence, then review and apply or reject that operation in Smart Inbox.

Name the next real comparison, the reference that should govern it, and the decision a proposal would help you make. Return to the proposal and review steps when that work is due.

The paid contribution to evaluate is that connected comparison and review. Context and Chat support preparation and continuity, but their usefulness alone is not a reason to keep paying for Connect Pro.

See current Pro options, including Connect Pro

Already have appropriate access? Return to the exercise with the next useful assignment rather than starting another plan.

Keep learning from the work behind the tools

This is one application of Smart Loop, not a complete system you have to adopt.

My emails explain useful decisions and practices from the products and workflows I build and use: how to direct larger assignments, maintain context, and use the result of one attempt to improve the next.

Get the lessons by email