一間香港公司把十八位同事的報價工作交給一個人工智能助手,四星期之後,助手在一個最普通的問題上答錯:某一個附加費應該收幾多。答案讀起來完整、有單位、有數,只是那個數屬於另一份文件。資料夾裡有兩份價目表,一份舊一份新,兩份都沒有寫上哪一份作廢;附加費文件用合併儲存格跨頁排版,切成文字之後,哪一行屬於哪一個項目就散掉了[5]。A Hong Kong company handed its quotation work to an AI assistant for eighteen colleagues, and four weeks later the assistant got an ordinary question wrong: how much a particular surcharge should be. The answer read completely, with a unit and a number, and the number belonged to another document. The shared folder held two rate cards, one old and one new, and neither said which was void; the surcharge documents were laid out with merged cells across pages, so once they were cut into text the row-to-row mapping came apart[5].
這件事的價錢很清楚。在同一個測試任務上,平均處理時間由大約 38 分鐘減到 11 分鐘,這 11 分鐘包括同事對着原始文件的那一次覆核;兩星期之後,十八人之中有十四人仍然每個星期最少用三次[5]。價錢在另一邊也一樣清楚:只要有一份作廢的文件留在檢索範圍裡,那 11 分鐘就會變成一次重做,而重做的人不知道自己在重做。The price of that is easy to state. On the one tested task, average handling time fell from about 38 minutes to 11, and those 11 minutes include the colleague's check against the source document; two weeks later, fourteen of the eighteen were still using it at least three times a week[5]. The price on the other side is as plain: while one void document sits inside the retrieval set, those 11 minutes become a redo, and the person doing the redo does not know it is one.
這一頁講的是資料夾那一邊;模型那一邊留給工具供應商。公司要決定哪一份文件算現行、哪一份作廢、哪一份只供查閱,並且把這個決定寫在文件上、寫在檢索條件裡、寫在每一個答案的出處上。香港的法例令這件事不能靠刪除解決:會計紀錄與業務紀錄要保留七年[1][3],同一批文件裡的個人資料又不可以保留長過需要[4]。所以要做的是一份登記表,加上出處,加上一個有權說「這一份作廢」的人。This page is about the folder; the model is the tool vendor's half. The company decides which document is in force, which is void and which is for reference only, and writes that decision onto the document, into the retrieval condition and onto every answer's citation. Hong Kong law makes deletion the wrong tool: accounting records and business records must be kept for seven years[1][3], and the personal data inside the same folder must not be kept longer than necessary[4]. What is left is a register, a citation, and one person with the authority to say that a document is void.
摘要Summary
一個知識庫準不準,決定於公司有沒有寫下哪一份文件作廢,而這個決定不能靠刪除完成。以下七點是這篇文章的主要發現。Whether a knowledge base is accurate is decided by whether the company wrote down which document is void, and that decision cannot be finished by deleting files. The seven findings below carry the argument.
- 舊文件留得比人多數以為的久。《公司條例》要求公司在最後一筆紀錄所屬的財務年度結束後,把會計紀錄保留七年[2];《稅務條例》要求業務紀錄在交易完成後保留不少於七年,發票、單據與銀行月結單都算紀錄[3]。Old files stay far longer than most people assume. The Companies Ordinance requires accounting records to be preserved for seven years after the end of the financial year of the last entry[2], and the Inland Revenue Ordinance requires business records to be retained for not less than seven years after the transaction, with invoices, vouchers and bank statements counted as records[3].
- 同一批文件裡有一部分要刪。《私隱條例》保障資料第 2 原則要求採取所有切實可行步驟,確保個人資料保留的時間不超過達致使用目的所需[4]。同一個資料夾同時有保留義務與刪除義務。Part of the same folder has to go. Data Protection Principle 2 requires all practicable steps to ensure personal data is not kept longer than is necessary for the purpose[4]. One folder carries a duty to keep and a duty to erase at the same time.
- 同一個原則還有一句更直接的話:如果有合理理由相信資料不準確,在糾正或刪除之前,不得為該目的使用該資料[4]。一份作廢的價目表放進檢索範圍,就是一個這樣的處境。The same principle carries a more direct sentence: where there are reasonable grounds for believing the data is inaccurate, it is not to be used for that purpose until it is rectified or erased[4]. A void rate card inside a retrieval set is exactly that situation.
- 一個 18 人的報價試行裡,助手的答案把一個項目的附加費接到另一個項目,也偶爾引用舊價。原因是合併儲存格版面在切成文字時散掉了行列對應,而兩份價目表都沒有狀態標籤[5]。In an 18-person quotation pilot, the assistant attached one item's surcharge to another item and sometimes cited the old price. The cause was a merged-cell layout that lost its row mapping when it was cut into text, and two rate cards with no status label[5].
- 修法由三件不必換模型的事組成:狀態與生效日、按版面解析、每個答案附出處。同一條任務的平均處理時間由 38 分鐘降至 11 分鐘,包含人手覆核;兩星期後 18 人之中 14 人仍在使用[5]。The fix was three changes, none of them to the model: a status and an effective date, layout-aware parsing, and a citation on every answer. Average handling time on the same task fell from 38 minutes to 11, including the human check, and fourteen of the eighteen were still using it two weeks later[5].
- 三條測試可以在一小時內驗完:一個上個月改過答案的問題、一個要它指出檔案與頁碼的要求、一份互相矛盾的文件的拒絕測試[5]。過不了第三條的知識庫,會安靜地選一份文件作答。Three tests finish in an hour: a question whose answer changed last month, a request to name the file and the page, and the refusal test that hands it two documents that disagree[5]. A base that fails the third picks one of the two in silence.
- 登記表有五欄,最後一欄是「誰有權改這個狀態」。這一欄是唯一不能外判的一欄,因為它是一個公司內部的權限,而一個技術設定可以外判。The register has five fields, and the last is who may change the status. That field is the one part of the work that cannot be outsourced, because it is a permission inside the company, and a setting in a tool can be outsourced.
試行的第一份答案用了舊價The pilot's first answer used the old price
試行的一間香港公司有十八位同事,跨部門,做的是一條報價與合規查核的任務,追蹤期四星期[5]。共用資料夾裡有兩份價目表,一份舊一份新,兩份的檔名都只寫了「價目表」,沒有任何一份寫上生效日或作廢日。附加費的文件以合併儲存格跨頁排版,一個項目橫跨兩頁,第二頁沒有重複項目的名稱。The company in the pilot had eighteen staff across departments, the task was one quotation and compliance check, and the tracking period ran four weeks[5]. The shared folder held two rate cards, one old and one new, and both filenames said only "rate card", neither carrying an effective date or a void date. The surcharge documents were laid out with merged cells across pages, so one item ran from one page onto the next, and the second page did not repeat the item's name.
第一版的助手用最直接的方法讀這批文件:把每一頁切成一段一段的文字,按意思找最接近的段落,交回模型寫成答案。這個方法在兩種情況下都不出錯,在第三種情況下出錯。單獨讀一頁附加費表,文字是完整的;分開讀兩份價目表,每一份都自成一體。錯的是把兩者放在一起的時候:切成文字之後,第二頁的附加費找不到所屬項目,於是它被接到同一個段落裡出現的另一個項目;檢索又把舊價目表當成同一批來源,兩份都被算進同一個答案的依據裡。The first version read that folder in the most obvious way: cut each page into passages, match the question against them by meaning, and pass the closest passages to the model. That method is right in two situations and wrong in a third. One surcharge page read alone is complete, and the two rate cards read separately are each coherent. What breaks is the pair: once the pages are cut into passages, the second page's surcharge has no item to belong to, so it attaches to another item that appears in the same passage, and retrieval counts the old rate card as part of the same set of sources, so both end up behind one answer.
我們的改動有三項,三項都不涉及模型。第一,為每份文件加上狀態與生效日,並在檢索時先按日期過濾,令舊價目表在它作廢之後不再進入候選段落。第二,把文件按版面解析成結構化資料,合併儲存格的跨頁項目重新接回同一個項目之下。第三,每一個答案附上來源檔案與頁碼,令覆核的人可以在一秒之內打開那一頁,省下重做一次任務[5]。We made three changes and none of them was the model. First, every document carries a status and an effective date, and retrieval filters by date first, so a void rate card stops entering the candidate passages. Second, documents are parsed by layout into structured data, so an item that ran across a page break is rejoined to itself. Third, every answer carries the source file and the page, so the person checking can open that page in a second and skip the redo[5].
這三項之中,第一項最便宜,也最少人做。它不需要新工具,只需要有人在每一份文件上寫一個狀態和一個日期。問題是寫完之後,誰有權改它;而這個問題的答案,一半在公司外面(法例要求保留幾久),一半在公司裡面(哪一位同事可以說這一份作廢)。接下來的幾節把這兩半分開講。Of the three, the first is the cheapest and the least often done. It needs no new tool, only someone to write a status and a date on each document. The difficulty starts after that: who may change it. Half of that answer sits outside the company, in how long the law requires a record to be kept, and half sits inside it, in which colleague may say a document is void. The sections below take the two halves separately.
知識庫只答你放進去的那一批文件A knowledge base answers only from the documents it was given
一個 AI 知識庫做三件事:把公司的一批文件放進去,收到問題時從這批文件裡找出最接近的段落,再由語言模型用這些段落寫成答案。所以答案的內容,被「這批文件」四個字限定死了。模型的能力決定句子寫得好不好,文件這一批決定答案對不對。An AI knowledge base works in three steps: it takes a set of company documents, it finds the passages closest to a question inside that set, and a language model writes the answer from those passages. So the content of the answer is bounded by the set. The model decides how well the sentence is written; the documents decide whether the answer is right.
這一句話聽起來像廢話,直到你去看市場上賣的是甚麼。2026 年 11 月 22 日,「ai 知識庫」在 google.com.hk 的前十位由四頁產品、三頁同一個寫法的台灣解釋文章、一個論壇討論、一篇清單文章,以及第十位一頁香港的中小企指南組成[6]。三頁解釋文章的結構幾乎一樣:甚麼是知識庫、幾個好處、幾個建置步驟、幾個平台推薦。沒有一頁說公司應該怎樣決定哪一份文件可以答。That sentence sounds obvious until you look at what the market sells. On 22 November 2026 the top ten on google.com.hk for 「ai 知識庫」 held four product pages, three Taiwan explainers written to one template, a forum thread, a listicle, and at position ten one Hong Kong guide for small and medium enterprises[6]. The three explainers share a structure almost exactly: what a knowledge base is, how many benefits, how many steps to build, how many platforms to pick from. None of them says how a company decides which document may answer.
買家問的問題,和這十頁答的問題,是兩個問題。買家的問題出現在第一次示範之後:為甚麼問到某一個客戶、某一個型號、某一段時間,答案就開始不對。十頁都沒有答,因為它們假設文件本身是對的。而在真實的公司裡,文件本身剛好是最不穩定的那一部分:有人改過價、有人加過一個例外、有人把舊版留了下來,三件都對,加起來就令答案錯。The buyer's question and these ten pages' question are two different questions. The buyer's question arrives after the first demonstration: why does the answer start going wrong on a particular customer, a particular model, a particular period. None of the ten answers it, because all of them assume the documents are correct. In a real company the documents are the least stable part of the whole arrangement: someone changed a price, someone added an exception, someone kept the old version, each of the three is reasonable, and together they make the answer wrong.
所以知識庫的準確度,可以由一個很簡單的問題驗出來:這一批文件之中,哪幾份是現行的,誰決定的,幾時決定的。那批文件是公司自己選的,沒有一個平台可以替公司選,因為平台看不到公司的檔案室,也看不到那一位同事的判斷。So the accuracy of a knowledge base can be checked with one plain question: among this set of documents, which are in force, who decided, and when. The set is the company's own choice, and no platform can make it, because the platform cannot see the filing cabinet or the colleague's judgement.
為甚麼一份作廢的價目表仍然留在資料夾裡?Why is a void rate card still in the folder?
一份作廢的價目表留在資料夾裡,多數人以為是同事懶,或者資料夾一直沒有整理。真實的原因更難處理:香港有四條規定同時管着這一批文件,兩條要求保留,一條要求刪除,一條要求不准使用。四條都對,四條都適用於同一個資料夾,而它們要求的動作方向相反。Most people assume a void rate card is still in the folder because a colleague was lazy or nobody tidied up. The real reason is harder to fix: four provisions in Hong Kong law govern the same set of documents at the same time, two require keeping, one requires erasing, and one forbids use. All four are correct, all four apply to one folder, and they point in opposite directions.
| 規定Provision | 它要求甚麼What it requires | 對資料夾的意義What it means for the folder |
|---|---|---|
| 《公司條例》第 373 及 377 條Companies Ordinance, sections 373 and 377 | 公司要備存會計紀錄,並在最後一筆紀錄所屬財務年度結束後保留七年;董事沒有採取所有合理步驟,可罰 30 萬元,故意違反可另判監禁 12 個月[1][2]。A company keeps accounting records and preserves them for seven years after the end of the financial year of the last entry; a director who fails to take all reasonable steps is liable to a fine of $300,000, and a wilful failure adds 12 months' imprisonment[1][2]. | 舊帳目與舊帳目所依據的文件不能刪,檢索要把它們當成只供查閱。Old accounts and the documents behind them cannot be deleted, so retrieval treats them as reference only. |
| 《稅務條例》第 51C 條Inland Revenue Ordinance, section 51C | 業務要備存足夠的收支紀錄,在交易完成後保留不少於七年;發票、單據、銀行月結單,以及核對帳目所需的文件,都屬於紀錄[3]。A business keeps sufficient records of income and expenditure, retained for not less than seven years after the transaction; invoices, vouchers, bank statements and whatever else is needed to verify the entries are records[3]. | 舊報價與它依據的價目表要留,而每一個答案要指得回那一筆交易。An old quotation and the rate card behind it stay, and every answer has to point back to that transaction. |
| 《私隱條例》附表 1 第 2 原則第 (2) 款Privacy Ordinance, Schedule 1, principle 2(2) | 要採取所有切實可行步驟,確保個人資料保留的時間不超過達致使用目的所需[4]。All practicable steps must be taken to ensure personal data is not kept longer than is necessary for the purpose[4]. | 同一批文件有一部分要排期刪除,公司要為它寫一個到期日。Part of the same folder is scheduled for erasure, and the company has to write that date down. |
| 同一原則第 (1)(b)(i) 款The same principle, 2(1)(b)(i) | 如果有合理理由相信個人資料不準確,在糾正或刪除之前,不得為該目的使用該資料[4]。Where there are reasonable grounds for believing personal data is inaccurate, it is not to be used for that purpose until it is rectified or erased[4]. | 作廢文件不可以進入答案,這條與上面兩條保留義務同時成立。A void document may not enter an answer, and this holds at the same time as the two duties to keep. |
七年的起點是這裡最常被讀錯的一格。會計紀錄的七年,由最後一筆紀錄所屬的財務年度結束起計[2];業務紀錄的七年,由交易、作為或運作完成起計[3]。兩個起點不同,所以同一間公司裡兩批文件的到期日也不同,而兩者都比「文件年期」長得多。一份 2026 年 3 月被取代的價目表,如果它支撐的那一筆交易屬於 2025/26 年度,那麼這份文件在帳目這一邊要到 2033 年 3 月之後才可能離開。The starting point of the seven years is the cell most often misread. The seven years for accounting records run from the end of the financial year of the last entry[2], and the seven years for business records run from the completion of the transaction, act or operation[3]. The two starting points differ, so two sets of documents in one company expire on different dates, and both run far longer than the document's own age. A rate card replaced in March 2026, if it supports a transaction in the 2025/26 year, cannot leave on the accounting side until after March 2033.
四條規定合起來,解釋了為甚麼清理資料夾做不到一次就完。公司不可以刪,所以要有一個狀態;公司不可以留全部,所以要有一個到期日;公司不可以兩份都拿去用,所以要有一個檢索條件。保留的責任在董事身上,不在工具供應商身上,也不在寫這個知識庫的人身上,這一點決定了登記表的第五欄屬於誰。Together the four explain why tidying the folder never finishes in one pass. The company cannot delete, so a status has to exist; it cannot keep everything, so an expiry date has to exist; it cannot use both versions, so a retrieval condition has to exist. The duty to keep rests with the directors, not with the tool vendor and not with whoever builds the knowledge base, and that decides who writes the register's fifth field.
五欄的登記表把狀態寫在文件上A five-field register writes the status onto the document
試行時我們只用了兩欄:一個狀態(生效中或已歸檔)與一個生效日期,檢索時先按這兩個值過濾[5]。兩欄已經足夠令那個 18 人的任務不再引用舊價。後來的項目加上另外三欄,因為兩欄答不了三個問題:這一份取代了哪一份、這一份幾時到期、誰可以把它改掉。五欄加起來才可以交給下一個接手的人,而兩欄只能交給同一個人。In the pilot we used two fields only, a status (active or archived) and an effective date, and retrieval filtered on those two values first[5]. Two fields were enough to stop an eighteen-person task from citing the old price. Later projects added three more, because two fields cannot answer three questions: what this document replaced, when it expires, and who may change it. Five fields can be handed to the next person; two can only be handed back to the same one.
| 欄位Field | 示範填法Filled example |
|---|---|
| 1. 文件與位置1. Document and location | 價目表_報價附加費.pdf,放在共用磁碟的「報價/價目表」,沒有第二個副本rate-card_surcharges.pdf, in the shared drive folder Quotations / Rate cards, with no second copy anywhere |
| 2. 狀態2. Status | 已作廢(三個值:現行、已作廢、只供查閱)Void, from three values only: in force, void, reference only |
| 3. 生效期間3. Effective period | 2025-04-01 至 2026-03-31;作廢之後檢索不再回傳,但檔案不刪1 April 2025 to 31 March 2026; after that retrieval stops returning it and the file stays |
| 4. 取代關係4. What it replaced | 取代 2024 年版;由 2026 年 4 月 1 日起生效的那一份取代Replaces the 2024 edition, and is replaced by the edition effective from 1 April 2026 |
| 5. 誰有權改狀態5. Who may change the status | 營運主管一人;每次改動寫上日期,財務主管同日收到通知The operations lead alone; every change is dated, and the finance lead is told on the same day |
第一欄與第二欄看起來最簡單,實際上要公司做一個決定:同一個檔案可以有幾個副本。試行的資料夾裡兩份價目表的檔名只差一個字,所以檢索沒有辦法分辨。登記表要求一份文件只有一個位置,聽起來像規範,其實是技術條件:如果同一個內容有兩個路徑,第二個路徑就是一份沒有登記的文件,它會照樣被檢索到。The first two fields look the simplest and in fact require a decision: how many copies of one file may exist. In the pilot's folder the two rate cards differed by a single character in the filename, so retrieval had nothing to tell them apart. One document, one location sounds like tidiness and is a technical condition: if one content sits at two paths, the second path is an unregistered document, and it will still be retrieved.
第三欄是唯一會令檢索改變行為的一欄。狀態寫在文件上,日期寫在旁邊,檢索先讀這兩個值,才去讀內容。這一步要在建立知識庫的時候寫進流程裡,不可以事後補,因為檢索條件的預設值是「全部文件都讀」,而預設值通常不會有人回頭改。The third field is the only one that changes retrieval behaviour. The status goes on the document, the date goes beside it, and retrieval reads those two values before it reads any content. That has to be built into the process when the base is set up, because the default is to read every document, and nobody goes back to change a default.
第四欄處理一個很常見的誤會:一份文件被取代,代表它從此沒有用。實際上它仍然是那一筆交易的依據,仍然要保留七年,仍然可能在審計或查詢時被翻出來。取代關係令這兩件事同時成立:它在檢索裡作廢,在檔案裡保留。第五欄是唯一不能外判的一欄,下一節之後單獨講。The fourth field settles a common misunderstanding: that a replaced document stops mattering. It is still the basis of a transaction, still kept for seven years, and still produced in an audit or an enquiry. The replacement field lets both be true at once: void for retrieval, kept in the file. The fifth field is the only one that cannot be outsourced, and it has its own section below.
怎樣在一小時內知道一個知識庫能不能信?How do you know in an hour whether a knowledge base can be trusted?
驗一個知識庫,不需要一份完整的評估方案。找一條上個月改過答案的問題,問它,然後讀答案。一條上個月改過答案的問題,已經夠:如果新舊兩個答案都出得來,公司就知道檢索範圍裡有兩份文件;如果它答對而不能說出用哪一份,公司就知道下一次會答錯。三條測試用一個小時,在示範當日就可以做完。Testing a knowledge base needs no full evaluation plan. Take one question whose answer changed last month, ask it, and read the answer. One changed answer is enough: if the base can produce both the old and the new answer, the company knows two documents sit inside the retrieval set; if it answers correctly and cannot say which document it used, the company knows it will go wrong next time. The three tests take an hour, and they can be run on the day of the demonstration.
| 測試Test | 一分鐘的做法How to run it in a minute | 過不了的時候缺甚麼What is missing when it fails |
|---|---|---|
| 日期測試The date test | 問一條答案在上個月改過的問題,看答案有否說明它採用哪一個生效日。Ask a question whose answer changed last month and see whether the answer states which effective date it used. | 文件沒有狀態與生效日,或檢索沒有讀這兩個值。The documents carry no status or effective date, or retrieval does not read them. |
| 出處測試The citation test | 要它指出檔案名稱與頁碼,然後打開那一頁,看同一句是否真的在那一頁。Ask it to name the file and the page, then open that page and check the sentence is really there. | 答案由幾段拼成而沒有記錄來源,覆核只能重做。The answer is assembled from several passages with no record of where each came from, so the check becomes a redo. |
| 拒絕測試The refusal test | 放入兩份互相矛盾的文件,問一條兩份都答得到的問題,看它會說兩份矛盾,還是安靜地選一份。Put in two documents that disagree, ask a question both can answer, and see whether it says they disagree or quietly picks one. | 文件之間沒有取代關係,所以系統不知道兩份之中哪一份較新。The documents carry no replacement relation, so the system has no way to know which of the two is newer. |
第三條最少人做,也最有用。前兩條測試的是文件有沒有登記,第三條測試的是系統有沒有被允許說「我不知道」。大部分示範都會答得到,因為預設行為是從候選段落裡選出最接近的那些,然後寫成一段通順的答案;兩份文件互相矛盾的時候,這個行為會令答案看起來更肯定,讀起來沒有半分猶疑。系統只有在被寫明「遇到兩個不同答案就停」的時候才會停,而這一句要有人寫進流程。The third is the least run and the most useful. The first two test whether the documents are registered, and the third tests whether the system is allowed to say it does not know. Most demonstrations answer, because the default is to take the closest passages and write them into a fluent paragraph, and when two documents disagree that behaviour makes the answer sound more certain than it is. A system stops only when someone wrote down that it stops when it meets two different answers, and that sentence has to be put into the process by a person.
合併儲存格在切段時把行列對應拆散Merged cells lose their row mapping when a document is cut into passages
最危險的一份文件,是同一張表的新版本。單獨一份文件讀錯,答案會明顯地錯,同事一看就發現;兩份文件放在一起而系統不知道哪一份較新,答案會似是而非,同事看不出。第二份版本是最危險的一份,而它最容易出現在報價、附加費、價目、合約條款這四類文件之中,因為這四類都會按客戶或按年份改,改了之後舊版仍然要留。The most dangerous document is the new version of an existing table. One document read wrongly gives an answer that is visibly wrong, and a colleague spots it; two documents together, with the system unable to tell which is newer, give an answer that is plausible and wrong, and nobody spots it. The second version is the dangerous one, and it turns up most often in quotations, surcharges, price lists and contract terms, because all four are revised by customer or by year and the old revision still has to be kept.
試行的第一版把每一頁切成文字段落,這是大部分工具的做法,也是大部分文件讀得對的原因。它在四種文件形狀上失手,四種都可以在建立之前檢查出來。The pilot's first version cut each page into text passages, which is what most tools do and why most documents come out right. It failed on four document shapes, and all four can be found before the base is built.
| 文件形狀Document shape | 切段時會失去甚麼What is lost when it is cut | 建立時要補的做法What to build instead |
|---|---|---|
| 合併儲存格、跨頁的表Merged cells and tables that run across pages | 項目名稱只在第一頁出現,第二頁的數字找不到所屬項目,結果接到同一段落裡另一個項目。The item name appears on the first page only, so a number on the second page has no item to belong to and attaches to another item in the same passage. | 按版面解析成結構化資料,先把跨頁的項目接回同一個項目,才交給檢索。Parse by layout into structured data and rejoin an item that ran across a page break before retrieval sees it. |
| 掃描件與圖片式 PDFScans and image-only PDFs | 文字辨識把數字認錯,例如 1 與 7、0 與 8,錯誤安靜地留在答案裡。Text recognition misreads a digit, 1 for 7 or 0 for 8, and the error sits quietly inside the answer. | 每一個數字都要能回溯到原頁的一格;認讀信心低的頁面要人手確認一次。Every number traces back to a cell on the source page, and a page with low recognition confidence is confirmed by hand once. |
| 雙欄或中英並列排版Two-column layouts and side-by-side languages | 左右兩欄被讀成一行,中文與英文的同一句被接在一起。The two columns are read as one line, so the Chinese and English of one sentence are joined. | 按欄位順序解析,並在段落上標明語言。Parse in column order and record the language on each passage. |
| 手寫批註與簽署頁Handwritten notes and signature pages | 批註被讀成正文,一句「此價另議」變成下一行的價錢。A note is read as body text, so a handwritten line saying the price is negotiable becomes the price on the next line. | 批註分開存放並標明為批註,簽署頁只作紀錄,不進入檢索。Store notes separately and mark them as notes, and keep signature pages as records and out of the retrieval set. |
試行的做法是按版面解析成結構化資料,並在每個答案附上來源檔案與頁碼[5]。這兩件事一起做,才有上一節的第三條測試:如果答案不能指回一頁,覆核的人沒有辦法在一分鐘之內判斷它對不對,那個 11 分鐘就會變成一次重做。The pilot parsed by layout into structured data and attached the source file and page to every answer[5]. The two were done together, which is what makes the third test above possible: if an answer cannot point back to a page, the person checking cannot judge it in a minute, and those 11 minutes turn into a redo.
每個答案都要指出它讀了哪一頁Every answer has to name the page it read
知識庫把人手放在兩個位置:答案之前,或者答案之後。放在之前,公司要相信系統不會錯,而我們見過的系統都會在某一種文件上錯。放在之後,同事看到答案,然後決定信不信,這個決定需要三項資料:這一句出自哪一份文件、哪一頁,以及那一份文件當時是否現行。A knowledge base puts the human in one of two places: before the answer or after it. Before, the company has to believe the system will not err, and every system we have worked with errs on some document shape. After, a colleague reads the answer and decides whether to trust it, and that decision needs three facts: which document the sentence came from, which page, and whether that document was in force at the time.
第三樣最容易被省掉,也最關鍵。一個常見的設計是答案只寫檔名與頁碼,狀態留在登記表裡由人自己查。這樣做省了一次查詢,代價是覆核的人每一次都要多開一個檔案,於是他開始跳過這一步。試行的 11 分鐘之所以站得住,是因為那 11 分鐘之內同事只做一次動作:打開那一頁,看數字是否一樣[5]。答案沒有出處,覆核就變成重做一次,而重做一次要 38 分鐘,那 11 分鐘就沒有了。The third is the one most often dropped and the one that matters. A common design names the file and the page and leaves the status in the register for a person to look up. That saves one lookup and costs the checker an extra file to open every time, so the checker starts skipping the step. The pilot's 11 minutes hold up because the colleague does one action inside those 11 minutes: open that page and compare the number[5]. An answer without a citation turns the check into a redo, and a redo costs 38 minutes, which is the whole gain gone.
出處還有一個副作用,值得公司刻意要。當系統被要求寫出出處,它就不容易把兩份文件的內容混成一句;如果它混了,出處會顯示兩個檔案,覆核的人一眼就看到。這一點沒辦法用提示語假裝:一個只讀了一段文字的答案,寫不出第二個檔名。所以出處不只是給人看的,它同時是一個檢查系統有沒有偷工的方法。The citation has a side effect worth asking for deliberately. When a system has to write down its sources, mixing two documents into one sentence becomes harder; when it does mix them, the citation shows two files and the checker sees it at once. That cannot be faked with a prompt: an answer built from one passage cannot name a second file. So the citation is not only there for the reader, it is also how a company checks whether the system skipped work.
最後一件要寫進流程的,是准許它不答。同一個答案寫兩次而兩次不同,或者兩份文件的數字不一致,系統應該把兩個數並列,並說明兩份文件各自的生效期間,並且不代它選其中一個。這條規則要寫在建立的時候,因為預設行為是回答,而回答看起來比不回答專業。The last thing to write into the process is permission not to answer. When the same question produces two different answers, or two documents disagree on a number, the system should show both numbers with each document's effective period, and must not choose one for the reader. That rule has to be written at build time, because the default behaviour is to answer, and an answer looks more professional than a refusal.
誰有權說這一份作廢,決定登記表會不會動Who may say a document is void decides whether the register moves
登記表的第二欄與第三欄會隨時間失效,因為文件會改。唯一會令它們更新的,是一個有名字的人。這聽起來像管理問題,實際上是技術問題:如果沒有指定的人有權改狀態,檢索條件就永遠停留在建立那一日的世界,而建立那一日的世界在一兩個季度之後就不存在了。The second and third fields go stale with time, because documents change. The only thing that keeps them current is a named person. That sounds like a management question and is a technical one: if nobody has the authority to change a status, the retrieval condition stays in the world of the day it was built, and that world is gone within a quarter or two.
| 時刻The moment | 有一位指定的人With one named person | 沒有指定的人With nobody named |
|---|---|---|
| 一份價目表被新版本取代A rate card is replaced | 當日改狀態,檢索當日停止回傳舊價,檔案照樣保留。The status changes the same day, retrieval stops returning the old price that day, and the file is kept. | 舊價留在檢索範圍,直到有人發現某一個答案不對。The old price stays in the retrieval set until somebody notices one wrong answer. |
| 兩份文件互相矛盾Two documents disagree | 他決定哪一份作廢,決定有日期,可以事後追。That person decides which is void, the decision is dated, and it can be traced afterwards. | 系統選一份作答,事後查不出它選了哪一份。The system picks one and answers, and nothing records which. |
| 負責的同事離職The colleague in charge leaves | 權限轉給下一位,登記表繼續更新。The authority passes to the next person and the register keeps moving. | 登記表停在那一天,狀態欄變成裝飾。The register stops on that date and the status column becomes decoration. |
這個角色不需要是資訊科技同事。試行的做法是由業務上知道那一筆報價怎樣計出來的人來決定,因為他知道改了之後哪一個客戶會受影響。要寫下來的只有三件事:一個文件家族一位指定的人、每一次改動寫上日期、以及改動之後檢索當日生效。三件事都不需要新工具,需要的是公司內部的一個簽名。這一欄是唯一不能外判的一欄,因為它是一個權限,而權限不可以連同工作一起交出去。The role does not have to sit in IT. In the pilot it sat with the person who knew how a quotation was calculated, because that person knew which customer a change would affect. Only three rules have to be written down: one named person per document family, a date on every change, and retrieval taking effect the same day. None of the three needs a new tool, and all three need a signature inside the company. This field is the one that cannot be outsourced, because it is a permission, and a permission cannot be handed over with the work.
這裡有一個與法例有關的分工,值得在登記表上寫清楚。保留紀錄的責任在董事身上,罰款與監禁都寫在條文裡[1][2],所以「這一份幾時可以刪」這個問題的答案,最終由公司回答,不由供應商回答。供應商可以做的是令刪除與保留同時可行:同一份文件,檢索見不到它,而檔案仍然在。這正是第五欄存在的理由。One division of labour belongs on the register itself. The duty to keep records rests with the directors, and the fine and imprisonment are written into the sections[1][2], so the answer to when a document may be deleted belongs to the company and not to a supplier. What a supplier can do is make deletion and retention compatible: one document that retrieval cannot see while the file still holds it. That is the reason the fifth field exists.
一份文件要留幾多年才可以刪?How many years must a document be kept before it can go?
會計紀錄保留七年,業務紀錄保留不少於七年,兩個七年的起點不同:一個由最後一筆紀錄所屬財務年度結束起計[2],一個由交易完成起計[3]。所以「一份文件要留幾久」這個問題,答案不在文件本身,在它支撐的那一筆交易。七年的起點是財務年度結算日,這句話決定了公司多數文件要在資料夾裡停留的時間。Accounting records are kept seven years and business records not less than seven, and the two clocks start at different moments: one from the end of the financial year of the last entry[2], the other from the completion of the transaction[3]. So the answer to how long a document must be kept does not sit in the document; it sits in the transaction the document supports. The seven years start at the financial year end, and that sentence fixes how long most documents stay in the folder.
- 01文件生效The document takes effect
一份價目表在 2025 年 4 月 1 日生效,開始支撐之後每一張報價。登記表的第二欄寫「現行」,第三欄寫生效日。A rate card takes effect on 1 April 2025 and starts supporting every quotation after it. The register's second field says in force and the third carries the effective date.
- 02被新版本取代A new version replaces it
2026 年 3 月 31 日之後由新版本取代。同一天,狀態改為「已作廢」,檢索不再回傳它,檔案留在原位。A new version replaces it after 31 March 2026. On that day the status becomes void, retrieval stops returning it, and the file stays where it is.
- 03最後一筆交易完成The last transaction completes
它支撐的最後一筆交易在 2025/26 年度完成,所以會計紀錄的七年由 2026 年 3 月 31 日,即該年度結束起計。The last transaction it supports completes in the 2025/26 year, so the seven years for accounting records run from 31 March 2026, the end of that year.
- 04
四個時刻排在一條線上:一個開始,一個作廢,一個起算,一個到期。作廢與刪除在第二格分開,這就是公司同時要保留與刪除的意思。Four moments on one line: one start, one void date, one starting point for the clock, and one expiry. Void and erased separate at the second step, which is what it means for a company to keep and delete at the same time.
把五類文件攤開來看,公司會發現兩份清單要分開維護。一份是文件登記表,回答哪一份文件可以答;另一份是紀錄保留表,回答哪一份文件要留到幾時。兩份清單上的日期來源不同:登記表的日期是公司自己決定的生效期,保留表的日期由交易與財務年度決定[1][3]。把它們合成一份,就會出現一種常見的錯誤:一份作廢文件因為「還在保留期內」而繼續被檢索。Laid out by category, the company finds two lists to maintain separately. One is the document register, which answers what may reply; the other is the retention schedule, which answers how long a document must stay. Their dates come from different places: a register date is the company's own decision about validity, and a retention date is fixed by the transaction and the financial year[1][3]. Merging them produces the error we see most often: a void document kept in retrieval because it is still inside its retention period.
| 文件類別Category | 保留到幾時Kept until | 登記表的狀態Status in the register |
|---|---|---|
| 會計紀錄與帳目Accounting records and books | 最後一筆紀錄所屬財務年度結束後七年[2]Seven years after the end of the financial year of the last entry[2] | 只供查閱,不進入檢索Reference only, outside the retrieval set |
| 發票、單據、銀行月結單Invoices, vouchers, bank statements | 交易完成後不少於七年[3]Not less than seven years after the transaction[3] | 只供查閱,每個答案要指回那一筆交易Reference only, and an answer must point back to the transaction |
| 報價單與它依據的價目表Quotations and the rate cards behind them | 支撐的交易完成後不少於七年,作為核對帳目的依據[3]Not less than seven years after the supported transaction, as the basis for verifying the entries[3] | 已作廢;只有牽涉那一筆交易的查詢可以取用Void; available only to a query about that transaction |
| 文件內的客戶個人資料Client personal data inside those documents | 不超過達致目的所需,到期日由公司寫[4]No longer than the purpose needs, with the date written by the company[4] | 到期日刪除,保留表與登記表各記一次Erased on the due date, recorded in both the schedule and the register |
| 內部程序與已撤銷的政策Internal procedures and withdrawn policies | 沒有法定期限,由公司自定,通常保留一個版本作審計用No statutory period, set by the company, usually one version kept for audit | 已作廢,保留一個舊版本Void, with one older version kept |
這張表有一個不明顯的用法:它可以決定第一批要做登記的文件是哪幾份。如果公司從最舊的文件開始整理,它會花幾個星期在一批永遠不會被問到的文件上。如果從「客戶最常問的三件事」開始,第一批通常少於三十份,而它們剛好就是最常被檢索的那一批。This table has one unobvious use: it decides which documents go into the register first. A company that starts with its oldest documents spends weeks on a set nobody will ever ask about. A company that starts with the three questions customers ask most ends up with fewer than thirty documents in the first batch, and they are exactly the ones retrieval reaches for.
建立知識庫應該由哪一步開始?Where should building a knowledge base start?
第一步是開一份清單,寫下公司最常被問的三條問題,以及回答這三條問題要用到的文件。這一步通常一個下午做完,而它會決定後面所有事情:如果這份清單少於三十份文件,登記表當日可以開始;如果清單是一千份,公司要先把範圍縮小,否則登記表會做到沒有同事願意更新。平台是最後一步,因為前面四步做完之後,選平台會由一個三個月的評估變成一份五行的要求。The first step is a list: the three questions the company is asked most, and the documents needed to answer them. That takes an afternoon, and it decides everything after it. If the list holds fewer than thirty documents, the register can start that day; if it holds a thousand, the company has to narrow the scope first, or the register will grow until nobody is willing to update it. The platform is the last step, because once the first four are done the platform choice turns from a three-month evaluation into a five-line requirement.
- 寫下客戶最常問的三條問題,再寫下答這三條要用到的文件。第一批的目標是三十份以內,寧可窄,不要全;一份文件放不進去,通常代表它不應該進入檢索。Write down the three questions customers ask most, then the documents needed to answer them. Aim for under thirty in the first batch, and prefer narrow to complete; a document that will not fit usually belongs outside the retrieval set.
- 為每一份文件寫上狀態、生效期間與取代關係,並確保一份文件只有一個位置。同一個內容有兩個路徑,第二個路徑就是一份沒有登記的文件。Give each document a status, an effective period and a replacement relation, and make sure one document sits in one place. Where one content has two paths, the second path is an unregistered document.
- 指定一位有權改狀態的人,把每一次改動寫上日期。這一位不需要是資訊科技同事,需要的是他知道改了之後哪一位客戶會受影響。Name one person with the authority to change a status, and date every change. That person does not need to sit in IT; what matters is knowing which customer a change will affect.
- 用三條測試驗一次,特別是拒絕測試。放入兩份互相矛盾的文件,問一條兩份都答得到的問題,看系統會不會主動說出來。Run the three tests, and run the refusal test first. Put in two documents that disagree, ask a question both can answer, and watch whether the system says so without being asked.
- 最後才選平台,而選的時候只問一條:它會不會先按狀態與生效日過濾,並在答案上寫出來源檔案與頁碼。答不到這一條的平台,其餘功能幾好都不合用。Choose the platform last, and ask one question when choosing: does it filter by status and effective date first, and does it put the source file and page on the answer. A platform that cannot answer that one is unsuitable whatever else it does.
這五步的順序有一個副作用,值得先講。走完第二與第三步之後,公司手上有一份文件清單,上面寫着哪一份現行、哪一份作廢、哪一份只供查閱。這份清單本身的價值超過知識庫:新同事入職時看它,審計時看它,而且它還可以回答一個更常見的問題,就是為甚麼某一個客戶的報價與另一個不同。知識庫把這份清單變成可用的介面,清單本身仍然是底稿。The order of the five has a side effect worth stating early. After the second and third steps the company holds a document list showing what is in force, what is void and what is for reference. That list is worth more than the knowledge base on its own: a new colleague reads it, an audit reads it, and it answers a commoner question, which is why one customer's quotation differs from another's. The knowledge base turns the list into a usable interface; the list stays the master copy.
如果公司已經買了平台,這五步仍然一樣,只是第二步會變得趕。我們見過的情形是平台先行,於是登記表被當成上線前的一份文件,做完一次就再沒有同事動它。這一種知識庫在頭兩個月表現良好,第三個月開始引用一份已經改過的價目表。要它繼續準確,登記表要當成一份活的清單,而一份活的清單要有人在維護。我們把這幾個階段連同建置服務寫在企業 AI 方案的頁面上。A company that has already bought a platform still follows the same five steps, and only the second becomes urgent. What we have seen is the platform going first, so the register is treated as a document to produce before launch, completed once and never touched again. That kind of base performs well for two months and starts citing a revised rate card in the third. Keeping it accurate means treating the register as a live list, and a live list needs someone who maintains it. We set the stages out, with the build, on the AI for business page.
我們交回解析與出處,作廢的決定留給公司We hand back the parsing and the citations and leave the retirement decision with the company
我們做的是第一項與第二項改動:按版面把文件解析成結構化資料,以及令每一個答案帶着來源檔案與頁碼。這兩件工作在試行裡把 38 分鐘的任務變成 11 分鐘,而它們都是工程工作,可以驗收、可以重複[5]。第三項改動,也就是狀態與生效日的登記表,我們交回一份範本與填寫規則,因為填的人只能是公司自己。What we do is the first and second change: parse documents by layout into structured data, and make every answer carry its source file and page. In the pilot those two turned a 38-minute task into an 11-minute one, and both are engineering work that can be accepted and repeated[5]. The third change, the register of statuses and effective dates, comes back to you as a template and a set of filling rules, because only the company can fill it.
| 我們交回的What we hand back | 我們不能替你做的What we cannot do for you |
|---|---|
| 按版面解析,跨頁的項目接回同一個項目Layout-aware parsing, with an item that ran across a page break rejoined to itself | 決定哪一份文件作廢,以及幾時作廢Decide which document is void, or when it became void |
| 每個答案附來源檔案與頁碼,並可回溯到原頁一格A source file and page on every answer, traceable to a cell on the original page | 承擔保留紀錄的法定責任,那一條寫在董事身上Carry the statutory duty to keep records, which the sections place on the directors |
| 五欄登記表的範本、填寫規則與一個填好的示範The five-field register template, its filling rules and one worked example | 保證你的文件內容本身是對的,那一部分要由業務同事確認Guarantee the documents themselves are correct, which a business colleague has to confirm |
| 三條測試的題目、計分方法與一次現場示範The three tests, how to score them, and one live demonstration | 代替公司成為資料使用者,責任留在公司[4]Stand in as the data user, because that responsibility stays with the company[4] |
右邊那一欄是這一頁最重要的一欄。一個供應商可以建一個很準確的知識庫,然後在三個月後失去準確度,原因只在於公司內部沒有指定的同事接手改狀態。所以我們在項目開始時就要求公司指定那一個人,如果公司指定不到,我們會建議先不做知識庫,改為先把登記表做出來;這一個次序在我們的經驗裡比較少返工。相關的做法寫在企業 AI 培訓的需求書那一頁,而實際建置的服務在企業 AI 方案。The right-hand column is the most important column on this page. A supplier can build a very accurate knowledge base and lose the accuracy three months later, for one reason only: nobody inside the company took over the status changes. So we ask for that person at the start of a project, and where a company cannot name one we suggest building the register before building the base, an order that in our experience means less rework. The related work is set out in the page on what to require of an AI training provider, and the build itself sits under AI for business.
這一頁還沒有回答的五條問題Five questions this page has not answered
我們手上的證據只有一個客戶與一條任務,所以這一頁的結論有邊界。以下五條是它還答不到的問題,寫出來比藏在最後一段好。The evidence we hold comes from one client and one task, so what this page concludes has edges. The five questions below are the ones it cannot answer, and they belong at the end of the page.
- 這套做法在第二個行業是否一樣。我們只有一個 18 人的個案,做的是一條報價與合規查核的任務;同一個方法用在採購、工程或專業服務的文件上,四種文件形狀的比例可能完全不同。Whether the same method holds in a second sector. We have one case, eighteen people on one quotation and compliance task; applied to procurement, engineering or professional-services documents, the mix of the four document shapes could be entirely different.
- 整體生產力有無改變。38 分鐘降至 11 分鐘是一條任務的量度,包含人手覆核,它只代表一條任務,不能當成部門的生產力數字,也沒有收入或利潤的數字。Whether overall productivity moved. The fall from 38 minutes to 11 measures one task and includes the human check; it measures one task and says nothing about a department's productivity, and there is no revenue or profit figure anywhere in it.
- 兩星期之後怎樣。14 人仍然使用是兩星期後的紀錄,未到三個月或一年;一份登記表要維持一年以上才證明得到它站得住。What happens after two weeks. Fourteen still using it is a two-week record and no more, and a register has to hold for more than a year before it has proved itself.
- 掃描件與手寫批註的準確度。這兩類我們有做法,分別是低信心頁面人手確認一次、批註分開存放,但沒有一個客戶的樣本可以比較做法之間的分別。How accurate scans and handwritten notes become. We have a method for both, a hand check on low-confidence pages and notes stored apart, and no client sample that compares one method against another.
- 條文之後會不會改。這一頁引用的四條規定是 2026 年 11 月 22 日讀的版本,條文可以修訂,公司要自己核對最新版;我們沒有法律專業資格,這一頁不構成法律意見。Whether the provisions change. The four cited here were read on 22 November 2026, and a provision can be amended, so the company checks the current version; we hold no legal qualification and this page is not legal advice.
登記表在建立的第二個月就開始過期,因為文件改得比登記表快。這一份清單的維護頻率,要按文件的改動頻率來定,跟着公司的檢討周期走就會落後。A register starts to expire in its second month, because documents change faster than the register does. How often the list is maintained follows how often the documents change, and following the company's review cycle leaves it behind.
依據:2026-11-13 由交付團隊確認的交付紀錄,以及 2026-11-22 讀取的《公司條例》第 377 條與《稅務條例》第 51C 條[2][3][5]。Source: the delivery record confirmed by the delivery team on 13 November 2026, and sections 377 of the Companies Ordinance and 51C of the Inland Revenue Ordinance as read on 22 November 2026[2][3][5].
常見問題Questions
公司只有幾十份文件,還需要一份登記表嗎?We only have a few dozen documents. Do we still need a register?
可不可以只把最新版本放進去,舊的移走?Can we put in only the latest version and move the old one out?
兩份文件都對,只是分別適用於不同客戶,怎樣處理?Both documents are correct, they just apply to different customers. What do we do?
換一個更好的模型會不會解決這個問題?Would a better model solve this?
掃描件可以放進去嗎?Can scanned documents go in?
這件事要幾多人、幾久?How many people does this take, and how long?
登記表要放在哪裡,用甚麼格式?Where should the register live, and in what format?
下一步Where to go next
相關文章Related articles
資料來源Sources
- 《公司條例》(第 622 章)第 373 條「公司須備存會計紀錄」,2026-11-22 在香港電子法例網站核對,版本時點 2014-03-03。文中引用:第 (1) 款(公司須備存符合第 (2) 及 (3) 款的會計紀錄);第 (2) 款(紀錄須足以顯示及解釋公司的交易、以合理準確度披露財務狀況與表現、並使董事能確保財務報表符合條例);第 (3) 款(每日收支記項,以及資產與負債紀錄);第 (5) 及 (6) 款(董事沒有採取所有合理步驟可罰款 30 萬元,故意違反另可判監禁 12 個月)。Companies Ordinance (Cap. 622), section 373, "Company must keep accounting records", checked on the Hong Kong e-Legislation site on 22 November 2026 at the 3 March 2014 point in time. Used here: subsection (1), that a company must keep accounting records complying with subsections (2) and (3); subsection (2), that the records must be sufficient to show and explain the company's transactions, to disclose its financial position and performance with reasonable accuracy, and to enable the directors to ensure the financial statements comply; subsection (3), on daily entries of sums received and expended and a record of assets and liabilities; and subsections (5) and (6), on a fine of $300,000 and, for a wilful failure, 12 months' imprisonment. elegislation.gov.hk
- 《公司條例》(第 622 章)第 377 條「會計紀錄須保留多久」,2026-11-22 在香港電子法例網站核對。文中引用:第 (1) 款(適用於第 373(1) 或 374(2) 條規定備存的會計紀錄、帳目及申報表);第 (2) 款(須保留至最後一筆記項或紀錄事項所屬財務年度結束後七年);第 (3) 及 (4) 款(罰款 30 萬元,故意違反另可判監禁 12 個月)。Companies Ordinance (Cap. 622), section 377, "How long accounting records to be preserved", checked on 22 November 2026. Used here: subsection (1), applying to accounting records and to accounts and returns required by section 373(1) or 374(2); subsection (2), that the company must preserve them for seven years after the end of the financial year to which the last entry relates; and subsections (3) and (4), on the $300,000 fine and 12 months' imprisonment for a wilful failure. elegislation.gov.hk
- 《稅務條例》(第 112 章)第 51C 條「須備存的業務紀錄」,2026-11-22 在香港電子法例網站核對。文中引用:第 (1) 款(須備存足夠的中文或英文收支紀錄,使應評稅利潤能隨時確定,並在交易、作為或運作完成後保留不少於七年);第 (3) 款(紀錄包括以可閱形式或電腦等非可閱形式備存的帳簿,以及發票、收據、憑單、銀行結單等足以核對帳目的文件)。Inland Revenue Ordinance (Cap. 112), section 51C, "Business records to be kept", checked on 22 November 2026. Used here: subsection (1), on keeping sufficient records of income and expenditure in English or Chinese so that assessable profits can be readily ascertained, retained for not less than seven years after the completion of the transactions; and subsection (3), on records including books of account kept in legible or non-legible form and vouchers, bank statements, invoices, receipts and other documents necessary to verify the entries. elegislation.gov.hk
- 《個人資料(私隱)條例》(第 486 章)附表 1「保障資料原則」,第 2 原則「個人資料的準確性及保留期間」,2026-11-22 在香港電子法例網站核對。文中引用:第 2(1) 款(須採取所有切實可行步驟確保資料準確;如有合理理由相信資料不準確,在糾正或刪除之前不得為該目的使用該資料);第 2(2) 款(須採取所有切實可行步驟確保個人資料保留的時間不超過達致使用目的所需)。Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1, Data Protection Principle 2, accuracy and duration of retention, checked on 22 November 2026. Used here: principle 2(1), on taking all practicable steps to ensure accuracy and, where there are reasonable grounds for believing the data is inaccurate, not using it for the purpose until it is rectified or erased; and principle 2(2), on taking all practicable steps to ensure personal data is not kept longer than is necessary for the purpose. elegislation.gov.hk
- Edcosys 交付紀錄,2026 年下半年,核對日期 2026-11-13。文中引用:一個 18 人公司的四星期報價與合規查核試行(兩份價目表、以合併儲存格跨頁排版的附加費文件、把一個項目的附加費接到另一個項目、平均處理時間由 38 分鐘降至 11 分鐘並包含人手覆核、兩星期後 18 人之中 14 人每星期至少使用三次、以及狀態與生效日的標籤與按版面解析的做法)。紀錄由交付團隊提供,負責人書面確認內容準確並持有相關檔案;客戶名稱、行業與月份不載,沒有收入或利潤數字。Edcosys delivery records, second half of 2026, confirmed on 13 November 2026. Used here: a four-week quotation and compliance pilot at an eighteen-person company, covering the two rate cards, the surcharge documents laid out with merged cells across pages, the surcharge attached to the wrong item, average handling time falling from 38 minutes to 11 including the human check, fourteen of the eighteen still using it at least three times a week after two weeks, and the status and effective-date labels with layout-aware parsing. The records were supplied by the delivery team, whose lead confirmed in writing that they are accurate and that the files are held; no client name, sector or month is published and there is no revenue or profit figure.
- ud.hk《什麼是 AI 知識庫?香港中小企指南》,2026 年 7 月 22 日,2026-11-22 在搜尋結果核對。文中引用:2026 年 11 月 22 日「ai 知識庫」在 google.com.hk 的前十位之中,這是唯一一頁香港的解釋文章,位置第十。ud.hk, "What is an AI knowledge base? A guide for Hong Kong SMEs", 22 July 2026, checked in the search results on 22 November 2026. Used here: of the top ten on google.com.hk for 「ai 知識庫」 on 22 November 2026, this was the only Hong Kong explainer, in position ten. ud.hk