Gate sheets, river runs, and client letters all pass the same desk at ShanDong WenSi Information Technology Co., Ltd. The six services below describe how the desk turns scattered records into a working archive that stays readable for years. Each service is described in plain language so you can decide which station to board first.
An archive sheet bay is the backbone of every engagement. We begin by laying out the current design sheets of a system in a single ordered bay so that every interface, every data field, and every decision is visible side by side. The bay is numbered by hand and cross-checked against an index rail, which means a reader can pull one sheet and immediately see which other sheets depend on it.
We build a bay for each major subsystem and we keep the bays in a fixed order along the shelf column. When a system changes, the new sheet is placed beside the old one rather than on top of it, so the history of the design remains readable. Clients often tell us that walking a bay for the first time is the moment the architecture finally becomes clear, because seeing the sheets together is different from reading them on separate screens. The full privacy terms for records in a bay are set out in our Privacy Policy.
An index note records why a system changed, who approved the change, and what the change was expected to achieve. We run index notes in short ordered sequences that follow a single thread from origin to close, so a reader who was not in the room can reconstruct the reasoning without a meeting.
Each run is numbered in the order the notes were written, and each note points back to the sheet it amends. Runs are kept short on purpose. A long run is hard to follow, so when a thread grows past a comfortable length we split it into a new run and record the link between them. Over time the runs become a history of the system that survives staff turnover, and they are the part of the archive our clients consult most often when they need to explain a past decision to a new team.
Every letter that reaches the desk passes a single clerk before it enters the archive. The clerk logs the letter, answers it in plain language, and files the reply beside the original so that the exchange can be found as one continuous record. A letter that arrives by post, by email, or through the contact form on this site all reach the same desk and the same clerk.
This small discipline removes the confusion that usually follows a request into a large organization. There is one name to call, one place to look, and one record of what was said. The clerk also keeps a running list of open letters so that a reply is never lost in a queue. When a request moves into a project, the letter desk hands the record to the archive sheet bay so that the conversation and the design stay connected, and you can send a letter to the desk here.
A reading window is a scheduled hour when a client sits at our JiNan desk and reads the actual system records with a clerk beside them. Nothing is summarized away and nothing is hidden behind a portal login. The client sets the pace, and the clerk answers questions as they come up or takes a note when an answer needs more work.
When a client leaves a window, they carry a printed reading slip that lists every sheet and note they reviewed. That slip becomes part of the record as well, so a later reader can see what was examined on which day. Reading windows are the clearest expression of the transparency we believe a systems firm owes its clients, and many long relationships began with a single window that showed the client the desk was telling the truth.
Twice each year the desk closes to outside requests and turns inward for an archive review round. The team reads the full shelf, compares each sheet against the live system, and writes a short report on the drift it found. Most rounds find only a handful of discrepancies, and a few find a serious one that justifies the practice on its own.
We treat the review not as an audit for blame but as maintenance for memory. Every finding is recorded, every correction is entered as a new index note, and the client receives the report with enough detail to decide what to do next. The round also gives us a chance to retire sheets that no longer describe anything real, which keeps the shelf honest and keeps the archive from growing into noise. A review round is a service in its own right, and clients can book one without being an active design client.
Every system retires eventually, and the retirement is where archives are usually lost. A stack desk sitting turns retirement into a deliberate act. The client sits with us at the stack desk, we walk through each record class together, and the client decides what to preserve, what to compress, and what to release under a written agreement.
The signed decision sheet is filed in the archive bay, so the reasoning behind a deletion is as well preserved as the records that remain. A sitting usually takes a single focused session, and it ends with a short written statement that the client can keep. When a merger or a closure forces a quick decision, a sitting is the fastest way to reach a defensible outcome without losing the records that matter. The responsibilities that sit on each side of a sitting are described in our Terms of Service.
You do not need to board at the first station. Some clients begin with a single sheet bay, some arrive only for a review round, and some come for a stack desk sitting after a merger. Write to the desk and tell us which records or systems you need help with, and we will suggest the station that fits.
Write to the desk →