You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/IMPLEMENTATION-LOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,3 +56,5 @@
56
56
- Performed a live Azure API attempt through the ONEVibe runtime. API health and sandbox route reachability were verified, and the provider began a real Kasm bootstrap; the request was cancelled before it returned a persisted sandbox ID. The test container was removed and no sandbox record remained. The required provider lifecycle remediation and success criteria are recorded in `ONECOMPUTER-LIVE-E2E.md`.
57
57
- Added bounded website-reference context. Users can attach HTTP(S) references through the composer; these are stored with the task, attached to agent context as untrusted material, and represented in evidence only by redacted origin/path metadata. ONEVibe does not fetch them automatically.
58
58
- Added bounded local-file task attachments. The browser reads selected files into the task request, the API validates/sanitizes and path-confines them under `inputs/`, and execution emits metadata-only evidence before presenting those files to the agent as untrusted input.
59
+
- Upgraded Website mode from a generic state demo to a responsive, portable enterprise landing-page starter with operating-boundary messaging, capability cards, and semantic FAQ disclosure. The next quality gate is agent-directed visual generation plus isolated browser/screenshot review.
60
+
- Elevated the Manus-style side artifact trail as a P0 interaction contract: every agent action should project a chronological terminal, browser/screenshot, file, diff, or artifact panel into the evidence-bound Computer rail. This remains observation-only: the browser must not receive X11, VNC, CDP, shell, or sandbox credentials.
Copy file name to clipboardExpand all lines: docs/MANUS-PARITY.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ This is the implementation gate, not a marketing checklist. **I** means behavior
43
43
## Creation modes and templates
44
44
45
45
29.**I** Create Slides mode — mode-specific plan, eight-slide outline, interactive preview, notes, and genuine PPTX output. ONEVibe also has explicit portable Document and Data-story modes with inspectable source/metadata.
46
-
30.**P** Build Website mode — website artifacts and isolated preview work; mode-specific workflow is pending.
46
+
30.**P** Build Website mode — portable React/Vite output now includes a responsive, accessible enterprise landing-page starter with clear operating-boundary messaging and semantic FAQ disclosure. AI-directed design, screenshot/browser review, richer template packs, and deployment remain pending.
47
47
31.**P** Design mode — concept rationale and design-token artifacts exist; richer visual generation is pending.
48
48
32.**P** Create Games mode — dedicated plan and a portable playable React interaction loop now exist; richer mechanics, game assets, and runtime play-testing remain pending.
49
49
33.**P** Expandable mode catalogue — the composer exposes nine purpose-specific modes with output descriptions and persists the chosen mode. A compact starter gallery now preconfigures editable Website, Briefing, Research, and Internal-tool tasks; deeper per-mode template packs remain pending.
@@ -109,7 +109,7 @@ This is the implementation gate, not a marketing checklist. **I** means behavior
109
109
84.**P** Sandbox-dashboard mockup — security context and a headless visual-runtime timeline are visible; inventory and management interaction are incomplete.
110
110
85.**P** Mobile-wallet mockup — deep link and approval card exist; wallet simulator/client is pending.
111
111
86.**I** Navigation interaction.
112
-
87.**M** FAQ accordion interaction as generated output.
112
+
87.**P** FAQ accordion interaction as generated output — Website mode includes semantic `details`/`summary` disclosure; agent-directed content and browser-reviewed interaction remain pending.
export default function App(){const [score,setScore]=useState(0);const [round,setRound]=useState(1);const [message,setMessage]=useState('Find the signal');const catchSignal=()=>{const next=score+round;setScore(next);setMessage(next>=12?'Signal secured — start a new round':'Signal captured');if(next>=12){setRound(1);setScore(0)}else setRound(round+1)};return <main className="game"><p className="eyebrow">ONEVibe playable prototype</p><h1>${task.title.replaceAll('`','')}</h1><section><div><span>Round</span><strong>{round}</strong></div><div><span>Signal</span><strong>{score}/12</strong></div></section><button className="signal" onClick={catchSignal}>✦</button><p>{message}</p><small>This local interaction is portable source. Any publish action remains subject to an external approval.</small></main>}
53
55
`
54
-
: `import { useState } from 'react'
56
+
: website
57
+
? `const title=${safeTitle}
58
+
const safeguards=['Isolated workspaces','Clear policy checkpoints','Evidence that travels with the work']
59
+
const questions=[['Can teams bring their own agent?','Yes. This starter is designed around an operating boundary, not a single agent vendor.'],['Who approves consequential actions?','A separate approval system should decide. The generated site never treats the browser session as approval authority.'],['What happens to the work?','Portable source, files, and task evidence remain available for review and handoff.']]
60
+
export default function App(){return <main><nav><a className="brand" href="#top"><i>◈</i> ONEVibe</a><div className="links"><a href="#approach">Approach</a><a href="#safeguards">Safeguards</a><a href="#faq">FAQ</a></div><a className="nav-cta" href="#start">Explore the workspace <span>↗</span></a></nav><section id="top" className="hero"><p className="eyebrow">A GOVERNED WORKSPACE FOR CAPABLE AGENTS</p><h1>{title}</h1><p className="lede">Give people room to create with the agents they choose—while keeping meaningful controls visible, deliberate, and outside the browser.</p><div className="actions"><a className="primary" href="#start">See the operating model <span>↓</span></a><a className="secondary" href="#faq">Read the questions <span>→</span></a></div><div className="signal-card"><span className="pulse"/><p>Workspace boundary active</p><b>Policy and evidence connected</b></div></section><section id="approach" className="statement"><p className="eyebrow">BUILT FOR THE MOMENT AFTER THE PROMPT</p><h2>Useful work deserves a trustworthy place to happen.</h2><p>ONEVibe keeps the task, its workspace, and the evidence of what happened in one calm, reviewable surface.</p></section><section id="safeguards" className="safeguards">{safeguards.map((item,index)=><article key={item}><small>0{index+1}</small><h3>{item}</h3><p>{index===0?'One task receives a bounded place to work.':index===1?'Sensitive steps can pause for an independent decision.':'Source and context are ready for the next person to inspect.'}</p></article>)}</section><section id="start" className="callout"><p className="eyebrow">THE WORKSPACE</p><h2>Move quickly. Know where the boundary is.</h2><p>Start with a focused task. Keep the operational record close. Escalate only the actions that need a human decision.</p><a className="primary" href="#faq">Open the task brief <span>→</span></a></section><section id="faq" className="faq"><div><p className="eyebrow">COMMON QUESTIONS</p><h2>Designed to be understood.</h2></div><div>{questions.map(([question,answer])=><details key={question}><summary>{question}<span>+</span></summary><p>{answer}</p></details>)}</div></section><footer><span>ONEVIBE / PORTABLE WEBSITE STARTER</span><a href="#top">Back to top ↑</a></footer></main>}
0 commit comments