One assistant layer on a shared base

Key tools: search_law / get_law_text / legal_research / legal_analysis

Key tools: quick_stats / quick_trend / chain_compare_regions / fetch_kosis_excel

A. Planning and multi-AI cross-review

• Reviewing from a top-tier journal's angle: rather than relying on one model, review in parallel from three or more perspectives — Claude (logic and prose), GPT (structure and completeness), Gemini (data and factual accuracy).
• Cost-efficient division: long Claude/Gemini reviews run in Freedom at flat rate; GPT-side review plus collation, comparison tables and file saving are handled by Hermes.
• When shortlisting English titles, the academic rationale and the editor's-eye reasoning are analysed together before choosing.

B. Manuscript revision and redline under a strict style guide

• Automatic application of a strict academic style: passive voice for Methods (past passive), no personal subjects, no AI boilerplate, consistent number-and-unit notation.
• Division of labour: the intellectual work of shaping sentences goes to Freedom; applying the agreed edits without damaging the original formatting, and saving them, goes to Hermes.
• Possible anywhere: kordoc is on every device, so HWPX formatting can be edited from the Desktop or laptop too. Filing the result into the right folder automatically, however, is A's job.

C. Turning reading into permanent assets — Research Wiki & ECC Atlas

• Papers that have been read are accumulated automatically into the Research Wiki on the Mac, with cross-links generated.
• The ECC Atlas structures self-healing and ECC knowledge as a map, ready to cite when writing the background section of a proposal.
• Bulk translation and consistency-check drafts are produced in Freedom; the final accumulation and indexing is handled by Hermes.

A. Storing a short record of a research-expense meeting

• Only five fields are taken from the receipt: the receipt itself, date and time, location (Engineering Bldg. 2, Room 213), meeting duration (one hour, starting two hours before payment) and meeting content.
• They are kept in 회의비기록/ under the project directory (Projects/), alongside the original receipt.
• When settlement or reporting is actually needed, it is all pulled up at once and turned into a table or paperwork. The point is not to finish the minutes on the spot.

B. Live updates to research output and CV

• When a new paper is published, the DOI is verified through the Crossref API and added to the top of the official CV (.docx) in standard format, with a backup kept.
• Documents submitted to public agencies and the university are structured into metadata / text / Obsidian indexes for storage.

C. Korean public and academic forms (HWPX/PDF)

• Filling blanks in HWPX/PDF forms, placing seal and signature anchors automatically, masking personal data.
• When revising design codes (KDS) and standard specifications (KCS), korean-law cross-checks the cited provisions.
• The Desktop and laptop can do all of this too — in a hurry, grab whichever computer is in front of you.

A. Choosing a remote path to fit the situation

B. Knowledge intake

• Throw a link, article or paper you come across into Telegram and it is classified and indexed by topic into the Mac's store (Knowledge_Archive/).

C. Monitoring long-running jobs

• For bulk wiki translation or other long jobs, open the Mac's screen through Chrome Remote Desktop and watch without interrupting them.

Why B: the whole paper has to be read, so flat rate wins.

Situation: a submitted PDF arrives for review. The judgement stays entirely yours; the AI is used only as a second reader that looks for points you may have missed.

How it runs

Read Review_Manuscript_2026.pdf together with my own review draft (my_review_draft.md).
Leave my draft as it is; just find the points I may have missed.
1) Novelty against prior work, particularly self-healing cementitious composites —
   are there issues my draft does not raise?
2) Flaws in the experimental design (hydration period control, crack width measurement error, etc.)
   that I did not flag
3) Overclaiming without statistical significance testing that I did not flag
Mark each item as 'already in my draft' or 'newly found' and put it in a table
with the supporting page numbers. Do not rewrite my review.

Situation: during KDS/KCS revision committee work, reviewing a large old-vs-new provision comparison table, catching typos and citation errors, and finishing it in the official submission format.

Review ~/Documents/Standards_Revision/콘크리트_설계기준_개정안.hwpx.
1) Check terminology consistency in the revised provisions against the current code, and verify the
   numbering of cited external standards (use korean-law to confirm the parent statutes/codes)
2) Screen exhaustively for typos and grammatical errors and list the proposed corrections
3) Using kordoc, apply the corrections while preserving the original HWPX formatting (tables, fonts) 100%,
   and produce '개정_사유서_및_신구대비표.hwpx' in the required format.

What happens: kordoc parses the HWPX structure safely → korean-law cross-checks cited statute and rule numbers → typos, spacing and unit notation (MPa, mm) inconsistencies are caught in bulk → kordoc.patch_document emits the finished file in the original format.

Why the Mac: the paper files and the ECC Atlas are there.

Situation: analysing 10–15 years of papers chronologically to trace how the research themes developed (e.g. ECC mix design → self-healing performance evaluation → ML-based multiscale prediction) for a large grant proposal.

Analyse the abstracts and conclusions of all 20 of my papers in
~/Documents/Research_Papers/My_Published_Papers/.
1) Chart the evolution of my core research themes from the early 2010s to now as a timeline (research roadmap).
2) Identify the key problems I have solved and the research gaps that remain open.
3) Write the result as text I can drop straight into section '1. Need for the research and prior work'
   of a new grant proposal.

Why A: the result has to be saved as a file.

Read and analyse 5 representative papers of mine in
~/Documents/Research_Papers/My_Published_Papers/.
1) The paragraph structure across introduction, body and conclusion
2) The English academic expressions and verb patterns I use most often
3) My style for figure/table captions and for sentences comparing numbers
Organise all of this and save it as a file called 'manuscript_writing_guide.md'.

Situation: using the literature notes you have accumulated in the research Wiki (LLM Wiki) as the basis for arguing a gap in your next grant proposal.

Based on the literature notes in Research_Knowledge/llm_wiki/, identify where the literature
is still thin (the research gaps) in the area of self-healing performance evaluation.
Put it in a table with links to the supporting references inside the Wiki,
so I can use it in my next grant proposal.

Why the Mac: the automatic backup schedule runs there.

Sync the Research_Knowledge/llm_wiki/ and 집단연구2025/ folders I worked on today
to Google Drive via rclone right now,
and file the metadata for the 3 newly added papers into the Notion_연구논문관리 dashboard format.

Situation: after a meal or meeting with lab members, photograph the receipt and send it over Telegram.

The point: not to produce formal minutes on the spot, but to keep the minimum set of fields so they can be pulled up later, when settlement or reporting paperwork is actually needed.

[receipt photo attached]
집단과제2025. Meeting expenses, attended by [names]. Topic: how to configure multi-instance AI agents

Only five things are stored

What the assistant does

Pulling it up later

From the 집단과제2025 meeting-expense records, collect the ones from the second half of 2025
and put them in a table of date, location, duration, attendees, topic and amount,
with the receipts attached.

→ Only at this point does it become settlement paperwork or formal minutes.

Situation: you were refining a manuscript on the Lab Desktop, then left for a conference, and want to finish a thought that occurred to you on the way.

How: join the Desktop's Orca session with the Orca mobile app and carry on with the conversation still intact.

Situation: you've moved to the laptop but need to run something heavy, or the files you need are on the Desktop or Mac.

How: connect to the Desktop or Mac through Chrome Remote Desktop and work with their resources and files directly.

• Connecting to the Mac gives you Hermes, the MCP servers, the Research Wiki and the ECC Atlas on screen
• Also useful for monitoring long jobs such as bulk wiki translation without interrupting them