A context-engineering library for Agent work

Make the task
explicit before the Agent starts guessing.

Loka Context Harness is a family of Agent Skills, portable plugin files, and copy-paste meta prompts for turning under-specified work into a clear, bounded brief.

A practical response to vague work

“Research this.”
“Build that.”
For whom? Why? Under what limits?

Most AI work begins with missing context. The audience, decision, evidence standard, constraints, deliverable, and definition of success are left for the Agent to infer.

This harness makes those choices visible. It is not an Agent runtime, a model benchmark, or a promise to make every model smarter. It is a reusable way to set a working environment before work begins.

02 / SEE THE WORKING CONTEXT

Same task.
Clearer brief.

Watch one matched, 45-second comparison: the same Agent, task, and response limit first receive only the request, then receive Loka ACE Lite as working context.

This is a transparent illustration, not a claim that every model or task will improve. Read the prompts and inspect the raw outputs before drawing your own conclusion.

Read ACE Lite

03 / INSPECT A REAL RUN

Same request.
Two ways to begin.

The direct path answers immediately. The ACE Lite path first makes its operating context visible, then gives the plan. Both results below are complete recorded responses, not a promise of virality or universal model improvement.

Shared user request

I just launched a small AI tool for freelancers and I want it to go viral in the next 30 days. What should I do?

Path ADirect responseDeepSeek V4.1 Flash
# Getting Traction in 30 Days: A Practical Playbook

I can't promise virality — nobody can, and anyone who does is selling something. What I *can* give you is a realistic plan that maximizes your odds and builds compounding momentum even if you don't get a viral moment.

## First, an honest reframe

"Viral in 30 days" is a lottery ticket. The better goal: **get to your first 100–500 genuinely engaged users in 30 days**, and set up the conditions where virality *could* happen. Most "overnight" successes had months of groundwork.

## Week 1: Sharpen the wedge

- **Nail one specific user.** "Freelancers" is too broad. Pick a niche: freelance designers? copywriters? developers? Pick the one where your tool solves a painful, frequent problem.
- **Write a one-sentence pitch** a stranger would repeat to a friend. If you can't, the product positioning isn't ready to spread.
- **Make the first-run experience instant.** No signup wall before value. Virality dies at friction.

## Week 2: Seed where your users already are

- **Post where freelancers congregate:** relevant subreddits (r/freelance, r/webdev, niche ones), Indie Hackers, Twitter/X, LinkedIn, Discord/Slack communities, Facebook groups.
- **Lead with the problem, not the product.** "I built X" gets ignored. "Here's how I cut my invoicing time from 2 hours to 10 minutes" gets read.
- **Do it manually and personally.** 20 thoughtful posts/comments beat 200 spammy ones. Spam gets you banned and remembered badly.

## Week 3: Engineer shareability

- **Build a shareable artifact.** A free template, a calculator, a "before/after" result, a public leaderboard — something users *want* to show others. This is the single biggest lever for organic spread.
- **Add a lightweight referral loop** if it fits naturally (e.g., "invite a collaborator"). Don't bolt on a gimmick that annoys people.
- **Collect testimonials and screenshots** the moment you get them. Social proof is fuel.

## Week 4: Amplify what's working

- **Double down on the one channel showing traction.** Kill the rest.
- **Reach out to 10–20 micro-influencers or newsletter writers** in your niche. Offer free access, not a pitch. Personalize each message.
- **Consider a launch moment:** Product Hunt, a "Show HN," a niche newsletter feature. These are spikes, not strategies — use them to convert, not to save you.

## What actually drives virality (when it happens)

1. **Emotional hook** — relief, delight, "I need this."
2. **Low friction to try** — no signup, instant value.
3. **Built-in sharing** — the product or its output is inherently shareable.
4. **A specific audience** with a shared identity and places to talk.

## What to avoid

- Buying followers or engagement (kills trust, often detectable).
- Spamming communities — you'll get banned and burn your reputation.
- Chasing every channel at once.
- Treating a launch spike as success if retention is zero.

## The metric that matters

Track **activation and retention**, not signups. 50 users who come back beat 5,000 who never do. Virality without retention is a vanity spike.

---

If you tell me what the tool does and who it's for, I can get much more specific — actual channels, a draft pitch, and a week-by-week content plan.
Path BACE Lite appliedDeepSeek V4.1 Flash
# Applied Context

- **Objective:** Build a realistic 30-day growth plan for a newly launched AI tool aimed at freelancers, with "viral" reframed as a stretch goal rather than a guarantee.
- **Audience:** You (solo founder / small team), freelancers as end users.
- **Approach:** Prioritize distribution and proof over polish; sequence quick wins before bigger bets.
- **Constraints:** 30 days, small team, no paid budget assumed, no ability to guarantee virality.
- **Deliverable:** A week-by-week plan with concrete actions and a simple success metric.
- **Success check:** Specific, actionable, realistic for a small team, honest about uncertainty.

---

## First, a reframe

"Viral in 30 days" is not something you can plan for — it's a lottery outcome. What you *can* plan for is **distribution + proof + a shareable hook**, which is what makes virality possible and gives you a durable base if it doesn't happen. Treat virality as upside, not the goal.

**Assumption:** You have no meaningful existing audience and no paid budget. If either is false, tell me and the plan changes.

---

## The core strategy

Freelancers don't buy tools because they're new. They buy because the tool **saves them time or money on a specific, painful task**. Your job in 30 days is to make that pain + payoff obvious and put it in front of freelancers where they already gather.

---

## Week 1 — Sharpen the wedge

1. **Pick one job, not a category.** "AI tool for freelancers" is too broad. Narrow to one painful task (e.g., "turn a client call into a scoped proposal in 3 minutes"). Broad tools don't spread; specific ones do.
2. **Rewrite your landing page around that one job.** Headline = the outcome, not the feature. Add a 30–60 second demo video (screen recording is fine).
3. **Add a frictionless entry point.** Free tier, no signup wall for the first use, or a "try it on this example" button. Every extra step kills sharing.
4. **Instrument it.** Add basic analytics so you know where people drop off. You can't optimize what you can't see.

## Week 2 — Seed where freelancers already are

1. **Identify 5–10 communities** where your target freelancer hangs out (subreddits, Slack/Discord groups, LinkedIn, niche forums, Indie Hackers).
2. **Participate before you promote.** Answer real questions for a few days. Then share your tool only where it genuinely solves the problem being discussed.
3. **Do 20–30 direct outreach messages** to freelancers who publicly complain about the exact problem you solve. Personal, specific, no copy-paste spam.
4. **Collect 5–10 real testimonials or before/after examples.** Proof is the fuel for every later channel.

## Week 3 — Create shareable content

1. **Make one "show your work" piece:** a short post or video showing the tool solving a real freelancer problem end to end.
2. **Build a free, useful asset** tied to your tool (template, checklist, calculator). Free value gets shared; ads for your tool don't.
3. **Post consistently on 1–2 platforms** where your users actually are — not all of them. Depth beats spread.
4. **Ask early users to share** with a specific, easy ask ("send this to one freelancer who'd find it useful").

## Week 4 — Amplify what's working, cut what isn't

1. **Double down on the one channel that produced the most signups.** Kill the rest.
2. **Reach out to 5–10 micro-creators or newsletter writers** in the freelancer space. Offer free access, not payment, and make it easy for them to cover you.
3. **Launch on one relevant platform** (Product Hunt, a niche community, or a newsletter) — but only if you have proof and a polished page ready.
4. **Write a short "what I learned launching" post.** Founder stories travel further than product announcements.

---

## What actually drives sharing

- **A visible result** someone can screenshot or show a client.
- **A specific audience** that recognizes itself ("this is for freelance designers who hate scoping").
- **Low friction** to try and to recommend.
- **A story** — why you built it, what it replaces.

## What to avoid

- Spraying the same post across every platform.
- Paid ads before you have proof and retention.
- Chasing "viral" at the cost of a product people actually keep using.
- Fake urgency or inflated claims — freelancers are skeptical and networked.

---

## How to judge success (realistic)

- **Good 30 days:** 100–500 real signups, 10–30 active users, 5+ testimonials, one channel clearly working.
- **Great 30 days:** a piece of content or a community post that brings a sustained trickle of signups.
- **Viral:** possible, not plannable. If it happens, your job is to have onboarding ready to catch it.

**One honest caveat:** I can't verify current platform rules, community norms, or what's trending right now — check those yourself before posting, since they change fast.

If you tell me the specific task your tool solves and where your first users came from, I can tighten this into a concrete day-by-day plan.

What the ACE path establishes before execution

  • Objective
  • Audience
  • Approach
  • Constraints
  • Deliverable
  • Success check

One completion per path · temperature 0 · no output cap · no retries · illustrative example only.

Inspect the full method and outputs
Read the two-scenario, three-model evidence report

04 / DEEP RESEARCH, WITHOUT THE MAZE

One public file.
One clear starting point.

For a chat Agent, begin with the Deep Research protocol. It uses Loka ACE to turn a question into evidence, uncertainty labels, competing explanations, risks, and next validation steps.

Copy into a chat Agent that can open public raw links
Use this Loka Deep Research protocol as your operating instructions:
https://raw.githubusercontent.com/Wazifati/loka-context-harness/main/DEEP_RESEARCH_START.md

My research task: [write your question here]
Read the protocol

05 / PICK THE ENVIRONMENT

Use one route.
Not one giant prompt.

Full and Lite are alternatives. V12 is the only designed overlay, and its Supervised and Autonomous editions are alternatives.

See the complete route map

06 / INSPECT BEFORE YOU ADOPT

Credibility
is verifiable.

The repository preserves original source materials, labels its Agent-ready adapters, and separates a synthetic dry-run from any claim about Agent performance.

Read the factual inventory, follow the five-minute evaluation path, and decide whether a specific route serves a real task.

Evaluate the harness

07 / MAKE THE LIBRARY BETTER

Bring your real
Agent experience.

Help with examples, compatibility reports, translations, documentation corrections, reproducible bugs, and carefully scoped adapters. Preserve the original materials, keep routes distinct, and support effectiveness claims with a reproducible method.