Milestones
List view
Decision and bounded-prototype gate for the in-house Sheet engine, granular collaboration, references, selective undo and durable recovery. Parent #520. No implementation acceptance or release date.
No due date•1/14 issues closedHuman decision 2026-10-10: deliver one milestone at a time. ALL Executes are stopped while milestone/Issue organization is reviewed. This membership is planning, not permission to resume. Original Issue criteria, evidence, holds and full Goal remain. Only a completed original-criterion audit on exact local integration closes an Issue or milestone. No new feature is added merely because it is useful. Research is intake, not an automatic gate. No product push/deploy or date is authorized. Stage 5 of 6. WAIT_PREVIOUS_MILESTONE; implementation STOPPED. Closure: Original DB plus private asset capture/restore, fresh installation/startup and required privacy/account/operator/backup/update/recovery evidence. Preserve source and unresolved attempts. Follow original #322 SaaS AND internal-installation requirements; a local synthetic child is not whole operational acceptance. Unassigned original release requirements must be explicitly mapped before this milestone can close; do not invent a successful backup or deployment. Primary Issues: #414, #419. Order: 01 → 02 → 03 → 04 → 05 → 06. Existing #417 optional publication, Board/Diagram AND Sheet adopted planning, advanced features and research remain outside this first delivery train; their original commitments are preserved.
No due date•0/2 issues closedHuman decision 2026-10-10: deliver one milestone at a time. ALL Executes are stopped while milestone/Issue organization is reviewed. This membership is planning, not permission to resume. Original Issue criteria, evidence, holds and full Goal remain. Only a completed original-criterion audit on exact local integration closes an Issue or milestone. No new feature is added merely because it is useful. Research is intake, not an automatic gate. No product push/deploy or date is authorized. Stage 4 of 6. WAIT_PREVIOUS_MILESTONE; implementation STOPPED. Closure: Original four-product/two-user PostgreSQL/API/product UI/Yorkie acceptance: convergence, reconnect/restart, per-user history/structure, current authorization and no snapshot overwrite of active collaborative content. Yorkie remains human-paused; milestone organization does not authorize its resume. No custom collaboration server or vendor changes. Primary Issues: #366, #367, #368, #371, #372, #373. Order: 01 → 02 → 03 → 04 → 05 → 06. Existing #417 optional publication, Board/Diagram AND Sheet adopted planning, advanced features and research remain outside this first delivery train; their original commitments are preserved.
No due date•0/6 issues closedHuman decision 2026-10-10: deliver one milestone at a time. ALL Executes are stopped while milestone/Issue organization is reviewed. This membership is planning, not permission to resume. Original Issue criteria, evidence, holds and full Goal remain. Only a completed original-criterion audit on exact local integration closes an Issue or milestone. No new feature is added merely because it is useful. Research is intake, not an automatic gate. No product push/deploy or date is authorized. Stage 3 of 6. WAIT_PREVIOUS_MILESTONE; implementation STOPPED. Closure: Finish original supported Note/Word/Slides/Site access/navigation/current-role/admin/native preservation/save/reopen/private raster contracts. Reuse the existing full engines. Actual source/compiled/OIDC/API/privatePG/S3 checks must match each original Issue scope. No generic new account invitation, billing, advanced editor or public Site publication. Paused #468/#479 do not resume from membership. Primary Issues: #369, #377, #378, #468, #479, #470, #412, #416, #509, #510, #511. Order: 01 → 02 → 03 → 04 → 05 → 06. Existing #417 optional publication, Board/Diagram AND Sheet adopted planning, advanced features and research remain outside this first delivery train; their original commitments are preserved.
No due date•1/11 issues closedHuman decision 2026-10-10: deliver one milestone at a time. ALL Executes are stopped while milestone/Issue organization is reviewed. This membership is planning, not permission to resume. Original Issue criteria, evidence, holds and full Goal remain. Only a completed original-criterion audit on exact local integration closes an Issue or milestone. No new feature is added merely because it is useful. Research is intake, not an automatic gate. No product push/deploy or date is authorized. Stage 1 of 6. Active planning priority after organization; implementation STOPPED. Closure: Original #493 DA1–DA6 plus its transition criteria: authenticated task/target/request → truthful generated proposal with source/version/reason/assumptions → explicit supported deterministic apply → confirmed save/reopen. Decline/cancel/stale/authority/input/recovery preserve complete native, history and fixed attempts. #508/#512 review-only and #504 schema adoption do NOT satisfy task-native Apply or save. Reuse #494 and the supported #273 contract; #420 unsafe Apply remains off. No new editor, desktop packaging, offline sync or arbitrary schema invention. Later-stage Note route/host/locale/auth foundations may be reused without requiring those broader Issues to close first. Primary Issues: #493, #494, #497, #498, #500, #501, #502, #503, #504, #506, #507, #508, #512, #513. Order: 01 → 02 → 03 → 04 → 05 → 06. Existing #417 optional publication, Board/Diagram AND Sheet adopted planning, advanced features and research remain outside this first delivery train; their original commitments are preserved. Prior milestone description retained as history: CANDIDATE internal authenticated-browser Note task experience under human-approved #493. One complete deliberate request -> actual proposal -> human review/decline -> explicit supported native apply -> confirmed save -> same-document reopen. Existing Note/Word/Slides/Site engines, native formats/rendering/history/current authority/save/recovery remain. Reuse #290 task/result/pin/receipt/execution records; no competing task/content store. Current local verification surface is the existing Office browser/OIDC/API/private PostgreSQL. Exact Codex clone, Electron/Mac-first/offline/package and all-four first-release inclusion are not adopted. No date, release promise, deployment, code push/PR or paid-service authorization. Actual issue membership is the candidate scope, not proof of readiness, execution or acceptance. First prerequisite: qualify one entire direct plain Note paragraph/single run replacement with existing FragmentEditor and exact native/history; then connect the task/request/model/review/save flow serially. Native qualification alone is not candidate success. Distinguish fixed test responses from actual model execution, original source from proposal, accepted intent from applied local content, save unknown from confirmed server result and separate later draft. Preserve failed evidence, stale/current-authority retirement and immutable retry lineage. Keep original broad #322/full13Goal external-alpha gates separate and intact, including four-product/two-user PostgreSQL/API/UI/Yorkie and existing privacy/account/operator/backup/installation/release conditions. All six Research milestone categories retain original scope; selected findings are intake, not automatic gates. #434 human-held/Yorkie paused/#420 unsafe Apply unavailable. Existing milestones6/7/8 and all original issue criteria remain retained; human-approved task-first direction supersedes old active priority prose only.
No due date•9/14 issues closedWonffice를 SaaS로 제공하기 위한 전체 아키텍처 연구. URL별 페이지·권한·상태, 데이터베이스·저장소 소유권, 인증·tenant 격리, API·Agent·협업, 배포·관측·백업·복구·보안·과금·데이터 생명주기를 현재 소스와 공식 문서로 정리한다. 구현됨·설계됨·가설·미검증을 구분한다. 기존 연구와 구현 이슈를 연결하고 중복·자동 기술 도입을 피한다. 연구 완료는 설계 검토 산출물 완료이며 구현·출시 승인이 아니다. 기존 마일스톤과 승인 우선순위를 보존한다.
No due date•0/3 issues closed## 목적과 종료 기준 Agent가 업무 문서 구조를 만들고 다른 Agent가 사용·수정하는 **첫 작은 Note 작업**이 실제 제품 경계에서 유용한지 판단한다. 완료는 Planner의 근거 있는 `가능 / 추가 검증 / 보류` 결정이다. 모든 장기 무인 자율성, 제품 구현 착수 또는 출시 완료가 아니다. 사전 승인된 안전한 순수 자료 변경에 routine 사람 확인을 필수 단계로 추가하지 않는다. 기한 없음. ## 순서와 소유 이슈 — 총 9건 1. [#472 발명 schema의 문법·원문 분리 인계 평가](https://github.com/barocss/barocss-editor/issues/472) — 신규. 2. [#471 버전 registry·손실 인지 migration](https://github.com/barocss/barocss-editor/issues/471) — 기존 이슈 재사용. 3. [#473 Note native 저장·재열기](https://github.com/barocss/barocss-editor/issues/473) — 신규. 4. [#474 선언형 view·안정 필드 편집](https://github.com/barocss/barocss-editor/issues/474) — 신규. 5. [#475 계산·제약·시간/가용량 의미](https://github.com/barocss/barocss-editor/issues/475) — 신규. 6. [#476 파생 view·자유 문장의 근거/stale](https://github.com/barocss/barocss-editor/issues/476) — 신규. 7. [#469 현재 권한·무화면 원자 적용](https://github.com/barocss/barocss-editor/issues/469) — 기존 이슈 재사용. 8. [#477 schema/data 경합·원자 예약](https://github.com/barocss/barocss-editor/issues/477) — 신규. 9. [#478 작은 Note 작업의 독립 결과·총비용](https://github.com/barocss/barocss-editor/issues/478) — 신규, 최종 go/no-go 자료. ## 기존 증거와 경계 [#467](https://github.com/barocss/barocss-editor/issues/467)의 빈 문서·Agent 인계·AST/시간 시험에는 실제 결과와 실패가 함께 있다. 엄격 날짜 규칙 후보 0/35·4/35, 문법 prompt 결함, 원문 archive confound, v4 host 편집(Agent 성공 아님)을 보존한다. [#466](https://github.com/barocss/barocss-editor/issues/466)의 원본 상충·격리 view/codec 연구는 제품 native 성공이 아니다. 입력 신뢰 [#465](https://github.com/barocss/barocss-editor/issues/465), 업무 의미 [#413](https://github.com/barocss/barocss-editor/issues/413), 일반 native/AI 계약/렌더러 [#459](https://github.com/barocss/barocss-editor/issues/459)·[#460](https://github.com/barocss/barocss-editor/issues/460)·[#461](https://github.com/barocss/barocss-editor/issues/461)·[#462](https://github.com/barocss/barocss-editor/issues/462)는 원래 소유·마일스톤에 남긴다. 각 시험은 관찰·제안·미검증과 비용을 나누고, 실패가 결정을 바꿀지 명시한다. 연구 이슈 등록만으로 Execute·PR·릴리즈·실제 외부 효과를 시작하지 않는다.
No due date•0/9 issues closedDEVELOPMENT LIBRARY RESEARCH. Research reusable technology contracts for document tools beyond Note, Word, Slides and Site: schema/editing policy/model/operation/transaction, renderer DSL, office-ui/office-editor-ui, native file/storage and collaboration. Use a fictional fifth document tool to test extension boundaries. Record exact source commit, confirmed facts, hypotheses, alternatives, compatibility and loss/recovery risk, and the smallest verification proposal. Planner decides adopt / validate more / defer, dependencies, value/cost and any later implementation or release issue. Research completion does not assign Execute, resume paused Yorkie work, prove four-product alpha, change release milestones or authorize code changes, external accounts, paid services, publication or deployment. Keep the existing Wonffice Research — 신규 기능 검토 milestone for product feature research and preserve existing implementation/release issue membership. No date is promised.
No due date•0/9 issues closed현재 Wonffice의 Workspace 자료함에서 Word·Slides·Site·Note 편집기로 열고 돌아오는 흐름과 각 문서에서 일어나는 AI 행위/UI를 계속 연구한다. 실제 문서 화면 또는 한 작업 흐름을 기준으로 관찰한다. 각 이슈에는 현재 화면/흐름, 출처와 기준 버전, 실제 화면 스크린샷 또는 GitHub에서 이해할 수 있게 렌더되는 그림·흐름도, AI 적용 화면안, 클릭 뒤 상태, 실패 시 다음 행동, 재사용 기능, 필요한 데이터 계약, 작은 검증안을 넣는다. 실제 Wonffice 캡처와 사용자가 제공한 다른 제품의 참고 화면과 허구 연구 그림을 구분하고 게시 뒤 렌더링을 확인한다. 공통 상단·선택·상태·복귀 규칙은 비교하되 Word·Slides·Site·Note의 고유 문서 구조와 도구는 유지한다. 새 프로젝트 대시보드나 임의의 전체 화면을 만들지 않는다. 연구·화면 스케치는 구현·사용자 검증·출시 완료가 아니다. 기존 Research에 근거를 전달한다. 중복 범위는 기존 이슈를 보완하고, 별도 화면 문제와 완료 기준이 있을 때만 새 이슈를 추가한다. 기존 릴리즈·Execute 순서는 바꾸지 않는다.
No due date•0/1 issues closed고객·구매자·반복 업무·시장 대안·SDK 도입·제품 투자·유료 가치와 비용의 근거를 모은다. 현재 연구 이슈 #289, #294, #295, #296, #326을 추적한다. 공개 공급자 기능과 가격은 Wonffice 고객 사용·지불 의사 증거가 아니다. 고객 관찰과 검증 결과는 사실·가설·미확인을 나눠 기록한다. 연구 완료는 구현·출시 완료가 아니며 Execute 착수나 우선순위 변경을 승인하지 않는다. Planner가 채택·추가 검증·보류, 선행 조건, 가치/비용, 최소 실험과 출시 후보 여부를 기존 이슈에 기록한다. 구현 제안 #337과 계측 구현 #297은 별도 범위를 유지한다. 기존 신규 기능 연구 milestone #5의 기능 연구 이슈는 유지한다. 일정은 증거와 사용자 결정 후 정한다.
No due date•0/5 issues closedUNSCHEDULED, not an active implementation or adopted release scope. Existing proposals, future extensions, documentation and retained defects are here until Planner checks purpose, dependency, original acceptance, value/cost and release necessity. Membership neither deletes a requirement nor promises it in a release. A reproduced blocker may be moved to the necessary active/alpha milestone with a recorded reason.434 remains explicitly human-deferred: do not implement, merge, expose or resume it from this membership. New editor roadmap commitments remain commitments; their precise scope/order/date are not invented here. Actual Issue/PR membership is the scope list. Membership is planning, not implementation, acceptance or delivery. Keep each Issue's original criteria. One existing serial Execute; do not restart or interrupt live443. Add to ACTIVE only a reproduced blocker or necessary acceptance work. Research remains separate; adoption needs a scoped existing Issue or a justified linked child. Preserve source-specific evidence and failed baselines. No release date is set. No code push, PR merge, deployment, paid service, additional access or customer transmission is authorized. External alpha retains all13 Goal requirements and original322 gates, including actual four-product/two-user PostgreSQL/API/UI/Yorkie, privacy/account/operator/backup/installation/release and both SaaS/internal installation. Yorkie stays paused; selected-object history434 stays human-deferred.
No due date•0/36 issues closedCANDIDATE, not assigned or release-ready. Audience: internal content author with fictional Note/Site. Flow: author a Note, derive a Site draft, edit Site-specific content, change Note, inspect supported differences/conflicts, deliberately save a new Site copy, reopen and identify origin/state while preserving the old Site and independent edits. No automatic three-way merge, publication or customer delivery. Keep291 original copy/version/partial-save/recovery criteria,407 exact seven authenticated Site/nested-body/awaited-flush/native/ACL/retry/restart criteria and432 final authenticated Site UI acceptance. Preserve407 WIP and separate430. Readiness review follows the active experience and a fresh preserved-work audit. Stop on overwrite, wrong nested identity, orphaned partial copy, duplicate effect or access loss; preserve originals and retry evidence. Actual Issue/PR membership is the scope list. Membership is planning, not implementation, acceptance or delivery. Keep each Issue's original criteria. One existing serial Execute; do not restart or interrupt live443. Add to ACTIVE only a reproduced blocker or necessary acceptance work. Research remains separate; adoption needs a scoped existing Issue or a justified linked child. Preserve source-specific evidence and failed baselines. No release date is set. No code push, PR merge, deployment, paid service, additional access or customer transmission is authorized. External alpha retains all13 Goal requirements and original322 gates, including actual four-product/two-user PostgreSQL/API/UI/Yorkie, privacy/account/operator/backup/installation/release and both SaaS/internal installation. Yorkie stays paused; selected-object history434 stays human-deferred.
No due date•1/3 issues closedHuman decision 2026-10-10: deliver one milestone at a time. ALL Executes are stopped while milestone/Issue organization is reviewed. This membership is planning, not permission to resume. Original Issue criteria, evidence, holds and full Goal remain. Only a completed original-criterion audit on exact local integration closes an Issue or milestone. No new feature is added merely because it is useful. Research is intake, not an automatic gate. No product push/deploy or date is authorized. Stage 2 of 6. WAIT_PREVIOUS_MILESTONE; implementation STOPPED. Closure: Finish the original stable requirement/decision/design and typed relation/version/confirmed-criterion/independent-result contracts. Original #505 and #444 remain finite existing scopes. #444 includes actual Word preview/reject/accept/save/reopen, so its whole acceptance belongs here, not Note-only Stage1. Preserve already accepted evidence; all Issues closed does not replace whole-milestone user-flow verification. Primary Issues: #423, #428, #431, #449, #450, #505, #444. Order: 01 → 02 → 03 → 04 → 05 → 06. Existing #417 optional publication, Board/Diagram AND Sheet adopted planning, advanced features and research remain outside this first delivery train; their original commitments are preserved. Prior milestone description retained as history: CANDIDATE, not assigned or end-to-end accepted. Audience: internal business-document tester with fictional rich Word. Flow: record one requirement before a decision exists; deliberately link a later decision; preserve stable IDs and exact historical pins; confirm an exact supported criterion; compare an actual work result with it and retrieve the independent result. Existing complete-pair/confirmation/registered-verifier acceptances remain source-specific foundations. Registered fictional verification is not actual-work verification. Readiness needs original native/pin/copy/authority/recovery criteria and independent expected outcomes; no generic schema platform or borrowed human approval. Review capacity and dependencies at a safe boundary after the active experience; no calendar delivery commitment. Stop and preserve records on changed pin bytes, reassigned IDs, duplicate results or denied-read leaks. Actual Issue/PR membership is the scope list. Membership is planning, not implementation, acceptance or delivery. Keep each Issue's original criteria. One existing serial Execute; do not restart or interrupt live443. Add to ACTIVE only a reproduced blocker or necessary acceptance work. Research remains separate; adoption needs a scoped existing Issue or a justified linked child. Preserve source-specific evidence and failed baselines. No release date is set. No code push, PR merge, deployment, paid service, additional access or customer transmission is authorized. External alpha retains all13 Goal requirements and original322 gates, including actual four-product/two-user PostgreSQL/API/UI/Yorkie, privacy/account/operator/backup/installation/release and both SaaS/internal installation. Yorkie stays paused; selected-object history434 stays human-deferred.
No due date•5/7 issues closedCurrent product priority superseded by human-approved #493 task-centered transition. The first internal candidate is milestone15 Note task to reviewed saved result. This former Word experience retains its existing issue membership, original criteria and source-specific accepted/unaccepted evidence; it is not the current execution slot. No closure, implementation replay, scope deletion or release promise. Previous description preserved verbatim as historical planning: ACTIVE internal experience, not external release-ready. Audience: owner/internal tester using fictional materials on an exact private local Office candidate. Flow: open project/result, select a supported Word range, record an opinion without inference, explicitly request a revision, inspect actual unsupported/proposal states, review a supported change or reject, save/reopen and retrieve original work evidence. Mixed-run opinion support is not arbitrary mixed-run model-application support. Readiness requires each assigned original criterion, exact native delta/history and current authority, lost-ACK/reload/restart recovery, final Node22 preflight and integrated affected reruns.443 integration was reported; Planner independent acceptance is separate. After any separately authorized delivery, retain the exact candidate, independent task results and defects. Stop on wrong target, native loss, duplicates or access violation; preserve drafts and known candidates. Operator/delivery owner and actual delivery are unconfirmed. Actual Issue/PR membership is the scope list. Membership is planning, not implementation, acceptance or delivery. Keep each Issue's original criteria. One existing serial Execute; do not restart or interrupt live443. Add to ACTIVE only a reproduced blocker or necessary acceptance work. Research remains separate; adoption needs a scoped existing Issue or a justified linked child. Preserve source-specific evidence and failed baselines. No release date is set. No code push, PR merge, deployment, paid service, additional access or customer transmission is authorized. External alpha retains all13 Goal requirements and original322 gates, including actual four-product/two-user PostgreSQL/API/UI/Yorkie, privacy/account/operator/backup/installation/release and both SaaS/internal installation. Yorkie stays paused; selected-object history434 stays human-deferred.
No due date•2/2 issues closedResearch operating rule: retain original research questions and evidence; Planner records adopt / validate more / defer. No research completion automatically starts Execute or proves release. Reuse the existing scoped implementation Issue first; create a linked child only for a confirmed missing scope. Keep research originals in this one research milestone. Screen/interaction Issues include a useful fictional design image or diagram, actions, exception states and acceptance; distinguish planning, current actual and verified implementation, and verify remote rendering. No hidden/private customer data or fake screenshot acceptance. Previous description retained as historical planning context: Wonffice 신규 기능 연구와 구현 가능성 검토를 모은다. Research가 사용자 문제, 조사 근거, 기존 구현과의 차이, 중복 여부, 최소 범위, 불확실성, 검증안을 연구 이슈로 기록한다. 기존 Planner는 가능/조건부 가능/현재 불가능/보류를 판단하고 선행 조건과 비용·우선순위를 기록한다. 채택한 기능은 연구 근거를 연결한 구현 이슈로 정리해 적절한 다음 릴리즈 마일스톤에 배치한다. 연구 검토 완료와 제품 구현·출시 완료를 구분한다. 연구 이슈 생성만으로 Execute 착수, 현재 우선순위 변경 또는 출시를 승인하지 않는다. 같은 목적의 연구는 기존 이슈에 보완하며, 새로운 근거 없이 이슈 수를 늘리지 않는다. 연구는 실제 최신 소스·이슈·PR·공식 자료를 확인하고 확인된 사실과 가설을 구분한다. 기간과 릴리즈 포함 여부는 Planner가 실제 검토 후 정한다.
No due date•0/15 issues closedFuture release stage, not active or release-ready. Retain the original scope below, but do not postpone any original322 external-alpha condition to a later release. Concrete inclusion, timing, owner, rollout, rollback and support require evidence and a release decision; no date or launch is set by this migration. Previous description retained as historical planning context: 정식 동시 출시: RC 통과, 차단 결함 없음, 설치·운영·복구 문서와 제품 소유자의 출시 결정.
No due dateFuture release stage, not active or release-ready. Retain the original scope below, but do not postpone any original322 external-alpha condition to a later release. Concrete inclusion, timing, owner, rollout, rollback and support require evidence and a release decision; no date or launch is set by this migration. Previous description retained as historical planning context: 기능 동결: 동시 편집·권한 회수·고객 기능 격리·업데이트·복원·관측·오프라인 내부 설치 검증.
No due dateFuture release stage, not active or release-ready. Retain the original scope below, but do not postpone any original322 external-alpha condition to a later release. Concrete inclusion, timing, owner, rollout, rollback and support require evidence and a release decision; no date or launch is set by this migration. Previous description retained as historical planning context: 제한된 고객 검증: 네 제품 저장·재열기·공유, 회사별 격리, 기본 백업·복구. SaaS와 내부 설치 동시 제공.
No due dateHuman decision 2026-10-10: deliver one milestone at a time. ALL Executes are stopped while milestone/Issue organization is reviewed. This membership is planning, not permission to resume. Original Issue criteria, evidence, holds and full Goal remain. Only a completed original-criterion audit on exact local integration closes an Issue or milestone. No new feature is added merely because it is useful. Research is intake, not an automatic gate. No product push/deploy or date is authorized. Stage 6 of 6. WAIT_PREVIOUS_MILESTONE; implementation STOPPED. Closure: Reconcile original #322 external-alpha requirements and original Goal parent contracts after stages1–5: same exact candidate, original four-product/two-user/Yorkie, both SaaS/internal installation, native/security/privacy/account/operator/backup/release evidence. #495/#290/#273 retain every original criterion; subset child completion is not parent acceptance. Separate Goal-parent evidence from release requirements: no research/optional backlog becomes a new release gate. No automatic release/deploy; existing final release authority and protection remain. Primary Issues: #322, #495, #290, #273, #262. Order: 01 → 02 → 03 → 04 → 05 → 06. Existing #417 optional publication, Board/Diagram AND Sheet adopted planning, advanced features and research remain outside this first delivery train; their original commitments are preserved. Prior milestone description retained as history: Current operating rule: FINAL EXTERNAL ALPHA gate, not the first internal preview. All original322/Goal native, four-product/two-user real PostgreSQL/API/UI/Yorkie and SaaS/internal-installation/privacy/account/operator/backup/release conditions remain required before external alpha. Not release-ready. Internal milestones are dependencies and do not reduce this scope. Previous description retained as historical planning context: 내부 검증: 기준점 CI, transaction 복구, 공통 작업 계약, 두 환경 설치·로그인·Note 서버 저장. 날짜는 검증 후 결정.
No due date•6/11 issues closed