DEV Community

Cover image for Stratagem #34: Derek Gave Up Acceptance Sign-Off. The AI Still Can't Tell Who Won.
xulingfeng
xulingfeng

Posted on AI-assisted

Stratagem #34: Derek Gave Up Acceptance Sign-Off. The AI Still Can't Tell Who Won.

Readers speculate on the final convergence

People do not injure themselves without cause; the wound must be real. Mix truth with falsehood, and the deception can succeed.

The Thirty-Six Stratagems, Inflicting Injury on Oneself


Previously on this series:

#15: Derek and Alex Shared One Server. Derek discovered that ACL's collector was mirroring diagnostic results, supply-chain orders, and patient-management metadata in full. He worked with Alex to redirect its output. The diagnostic results took a separate route back into the internal pipeline.

#27: Alex Watched the AI Wait. The 800 ms experiment ended. During that call, Alex confirmed that his observation probe was still running.

#33: Mark Reviewed an AI Method. The Reviewer Brought Back a Different Question. The technical conclusion was retained within defined limits. Its supporting sources still needed verification. Mark had not yet sent his request for permission.


Two Names

The lunch bag rested against the monitor stand, still sealed. Derek dragged the schedule across the screen and stopped the cursor over an empty slot. The page header read MediSys's AI-Assisted Diagnostic Validation Platform. His name was in the Quality Validation Lead field.

A new email notification covered one corner of the schedule. The Project Management Office (PMO) had sent a maintenance brief and responsibility matrix for an old hospital integration project. The work package was COL-OUT-04. He was to confirm the external delivery arrangements that afternoon.

Execution owner: Derek Shaw. Acceptance signatory: Derek Shaw. Beneath the names, a note said that closing the package under the normal process required the signatory to confirm the validation results and any outstanding items. The existing authorization remained in effect.

The scope covered only the collector component's output path to a designated test receiver, using an isolated environment and synthetic data. It excluded the diagnostic pipeline and production deployment. Two afternoons were reserved. The version, configuration, sample, and expected results had not yet arrived.

The meeting invitation named Evan Brooks as ACL's appointed delivery contact for this package. Derek put it aside and opened the old architecture diagram in _review. Three input lines fed the collector: diagnostic validation results, supply-chain orders, and patient-management metadata. An annotation said the hospital had authorized access. The input configuration mirrored all three streams in full, in real time.

He enlarged the patient-metadata line, then opened the screenshot taken after the output had been redirected:

# archived configuration screenshot; not current runtime state
output_dest: medisys_test_node.local/sandbox/
Enter fullscreen mode Exit fullscreen mode

A separate note showed the diagnostic results returning to the internal pipeline. That was a different change from redirecting the collector's output. Derek did not connect to the old gateway. He checked Evan's identity in the project directory, then asked the PMO to confirm the appointment, the data scope, and whether the old authorization carried over. The reply included the formal appointment. This package did not inherit the hospital's old access authorization. The version and configuration were still to come.

The video call connected. Evan shared the execution conditions sheet. Derek expanded the data-scope field.

“What does it read? Where does it send it?”

“Synthetic samples from the supplier. A separately configured test receiver. The address comes with the package.”

“No hospital gateway or patient-data interface?”

“Not in this scope.”

“List the inputs and the destination. Don't just write ‘audit data.’”

Evan added two fields. Derek shared the checklist and requested that no hospital access credentials be configured in the test environment. He also requested read-only access to the gateway connection records for this run. MediSys would confirm isolation and access permissions. Any parameters not yet available were left blank. He pulled up the responsibility matrix beside the checklist.

“Who executes, and who signs off?”

“Both are me at the moment. For this package only.”

Evan added a requirement to the conditions sheet: an authorized person who had not taken part in execution had to independently confirm the final results.

“Joint sign-off is fine. The other person has to review the results, not just acknowledge receipt.”

Derek noted “add independent confirmation,” crossed out the old address on the preparation sheet, and added the requirements for retaining the version, procedure, and sample.

“If I keep joint sign-off, you still provide the materials?”

“Yes. The appointment must be valid. We're not asking you to give up your acceptance sign-off authority.”

The meeting record captured that answer and the delivery conditions: the personnel arrangements had to be in place before delivery, and validation would not start until the version and configuration were available. Derek saved it and replied that he would notify them once the personnel arrangements were finalized.


Full Transfer

MediSys Vice President Morgan finished a call and checked the responsibility matrix Derek handed her against the existing authorization. She laid out two options: add an independent acceptance reviewer and retain Derek's joint sign-off, or transfer acceptance sign-off authority entirely, leaving him to execute and submit results.

She pushed the first form toward him. Both signatures would be needed for normal closure. Evan's confirmation that joint sign-off was acceptable lay beside it.

Derek's pen stopped over the first option, then moved to the second.

“Full transfer.”

Morgan looked up, her brows drawing together.

“They didn't ask you to go that far.”

“I know.”

A drill started outside. Morgan closed the window, returned to her desk, and opened the dispute-handling clause.

“Once this takes effect, the package can close without your signature. You can raise an objection. You can't hold it open by refusing to sign.”

“If a connection outside the approved list appears during execution, who stops it?” Derek asked.

Morgan opened the safety escalation clause. “Report it and pause under the existing rules. The new acceptance signatory decides whether the package can be closed under the normal process. Those are separate decisions.”

“What about the raw output? Is it kept after closure?”

“For the retention period. Upload the originals. Keep corrections traceable. And if you change the execution plan, tell me first. Don't do it and tell me afterward.”

Derek wrote both page numbers on the back of the form. Additional testing still needed approval. The existing safety reporting and suspension procedures remained in force. He remained responsible for retaining raw outputs, configuration records, and deviation records. He left the acceptance column alone.

Morgan put the smaller change back in front of him. His name was still in the joint-sign-off field. The drill stopped. She did not hurry him.

Derek set the first form aside, selected full transfer, added “no backup acceptance signatory,” and signed and dated it. Morgan took the application and returned a copy.

She opened MediSys's quality authorization register and selected Claire Bennett. Beside the name, Derek read her department and role: Quality, Acceptance Reviewer. Her authorization covered this category of work and was still valid. She was not on the execution team list. Morgan sent those records to the quality lead for verification, then asked Claire to confirm that she would not participate in execution and would accept the appointment.

The application showed PENDING APPROVAL. It would take effect only after project approval and the corresponding system permission updates. Until then, the old matrix still named Derek as signatory. The change covered this package alone. Other work was unaffected. There was no automatic restoration clause. Changing it again would require a new application. He tucked the copy into his notebook.


Effective

The quality lead confirmed that evening that Claire's authorization covered the work. The next morning, Claire accepted by email, confirmed that she would not take part in execution, and listed the materials to retain. She made no commitment about the acceptance outcome. The project approver then approved the appointment. The system permission update was still pending.

At 10:17, the notification arrived with the new revision of the responsibility matrix, its effective time, and confirmation that the permissions had been updated. Derek logged in again. He could still submit execution records. Acceptance sign-off was no longer available to him. He downloaded and printed the effective change record and put it in his notebook.

Derek opened a local directory, saved the two role exports as roles_before.json and roles_after.json, and opened them side by side. Both carried the package ID, responsibility revision, and approval status. He checked the new effective time, left the notification beside the files, opened a terminal, and wrote and ran a script comparing the two operations. It read only local files:

import json
from pathlib import Path

before = json.loads(Path("roles_before.json").read_text())
after = json.loads(Path("roles_after.json").read_text())
if before["work_package"] != after["work_package"] or after["work_package"] != "COL-OUT-04":
    raise ValueError("wrong work package")
if after["status"] != "effective":
    raise ValueError("role change not effective")

def holders(snapshot, action):
    return set(snapshot["actions"][action])

for action in ("submit_execution_record", "accept_work_package"):
    old = holders(before, action)
    new = holders(after, action)
    print(action)
    print("  after:", sorted(new))
    print("  removed:", sorted(old - new))
    print("  added:", sorted(new - old))
Enter fullscreen mode Exit fullscreen mode
submit_execution_record
  after: ['Derek Shaw']
  removed: []
  added: []
accept_work_package
  after: ['Claire Bennett']
  removed: ['Derek Shaw']
  added: ['Claire Bennett']
Enter fullscreen mode Exit fullscreen mode

The first operation had no additions or removals. Derek moved the cursor to the second, accept_work_package, and checked the updated list against the notification again. He saved the files and output. Morgan messaged: “Report issues as usual. Copy Claire.” He added her to the recipients and sent Evan the formal change link.

The supplier's full delivery package was still outstanding that afternoon. Derek released the first environment reservation and kept the following day's slot. A colleague borrowed the test machine. He turned to routine defects. When he left the office, the effective change record was in the notebook he took with him.


The Third Cup

A strip of reflected light slid across Derek's shoes as the glass door opened. The man was clearing cups from the counter. As he lifted each cup, a damp ring remained on the counter. He folded the damp cloth over and wiped a dry space.

Alex sat by the window with a latte. As Derek passed, Alex looked up and nodded. Derek nodded back, set his bag beside the counter, and pulled out the stool near the end. Alex lifted his cup. They did not speak.

Derek took out his laptop. The printed change record stayed in the paper notebook inside his bag. He opened the laptop, and the cold light from the screen fell across the back of his hand. In the local schedule, the slot he had released was empty. The next day's reservation remained. He opened the two role exports saved that morning side by side.

The grinder started, covering the tapping of keys. The man locked in the portafilter and pressed the switch. Coffee ran down the cup's inner wall, darkening as it filled. He added hot water for an Americano, put a coaster to the right of the laptop, set the cup on it, and removed the damp cloth beside Derek's elbow.

Derek took a sip. As he put the cup down, its base caught the coaster's edge. The man held the coaster steady until Derek released the cup. Steam rose across a corner of the screen and thinned beneath the pendant light.

The two exports showed that the list of people authorized to submit execution records was unchanged. Under acceptance sign-off, one showed Derek Shaw, the other Claire Bennett. Derek closed the old version and left the new one beside the schedule. He did not open a terminal.

The man came around the counter with a tray and cleared the neighboring table. At the window, Alex drew his cup closer. The man took only the empty water glass and returned to the sink. When Derek looked up from the screen, Alex had lowered his head and opened the notebook on his table.

The tap ran. The man tipped a cup, letting the last water slide down the porcelain into the sink, turned it under the stream, and set it upside down on the rack. A car passed outside. White light swept the window frame, briefly catching Alex's silhouette in the glass. The man shut off the tap. Only the coffee machine's low hum remained.

Derek finished his Americano and closed the laptop. The man came to collect the cup. Two empty cups clinked together on his tray. Derek put the money in the small dish and packed his laptop. His phone lit up.

Evan had verified the new arrangement. Delivery was expected that day. He asked Derek to confirm that he would use only the approved isolated environment.

Standing beside the stool, Derek replied: “Confirmed. New configuration. Not the old address.” He put away the phone and pulled on his jacket. The man stepped aside with the tray, clearing the way to the door. Derek pushed it open. The rain sounded suddenly closer.

At the street corner, the project system notified him that the complete package had arrived. Derek checked the ID and timestamp, turned, and headed back to the office.


Execution Conditions

Only the overhead lights above the desks nearest the corridor were on. The complete package had arrived twenty minutes earlier. Evan had copied Claire and the project channel, asking Derek to check the files and scope first. No remote-access invitation was included.

The delivery instructions read:

Please execute the approved cases and return the results against the listed acceptance criteria. Final sign-off will be handled separately.

Derek downloaded the attachments from delivery record DL-04-01 and extracted them into a local package directory. The responsibility revision matched the arrangement now in effect. At the package root, manifest.json listed the package ID, five relative paths, and a SHA-256 digest for each:

README.md
config/collector.json
fixtures/event.json
procedure.md
expected.json
Enter fullscreen mode Exit fullscreen mode

He wrote a script to check only the package paths, file set, and digests. He did not load the component or run commands from the procedure file.

import hashlib
import json
from pathlib import Path, PurePosixPath

root = Path("package").resolve()
manifest = json.loads((root / "manifest.json").read_text())
if manifest["work_package"] != "COL-OUT-04":
    raise ValueError("wrong work package")

files = manifest["files"]
if not isinstance(files, dict) or not files:
    raise ValueError("empty or invalid manifest")
for name, expected in files.items():
    relative = PurePosixPath(name)
    if (relative.is_absolute() or ".." in relative.parts
            or name != relative.as_posix()
            or not relative.parts or chr(92) in name):
        raise ValueError(f"invalid path: {name}")
    target = root.joinpath(*relative.parts).resolve(strict=True)
    if root not in target.parents or not target.is_file():
        raise ValueError(f"outside package or not a file: {name}")
    actual = hashlib.sha256(target.read_bytes()).hexdigest()
    if actual != expected:
        raise ValueError(f"checksum mismatch: {name}")

present = {
    p.relative_to(root).as_posix()
    for p in root.rglob("*")
    if p.is_file() and p != root / "manifest.json"
}
if present != set(files):
    raise ValueError("file list mismatch")
print(f"{len(files)} files matched manifest")
Enter fullscreen mode Exit fullscreen mode
5 files matched manifest
Enter fullscreen mode Exit fullscreen mode

He saved the result under “Package File Consistency Check.” The manifest came from the same package. The source-verification field remained unchecked. He checked the isolated test-service name in the configuration against the network-access request. The sample was labeled synthetic, not hospital data. The receiver was not the old address.

He entered the version in the record template, leaving execution time and actual result blank. He acknowledged receipt, then checked the printed change record again:

Execution: Derek Shaw.

Final acceptance: Claire Bennett.


One Output

The test machine was free the next afternoon. Derek logged in to isolated environment ISO-04, opened the environment approval and readiness confirmation, then brought up the mounts visible within the session, this run's connection configuration, and the credential inventory.

He put the preparation record on the right and filled it in one item at a time. At the destination field, he opened the gateway rules and compared them with the delivery configuration and approval:

ISO-04 / Preparation Record for This Run

Data mounts: synthetic sample directory
Hospital data directory: not visible
Hospital access credentials: not listed in this run's connection configuration or inventory
Configured destination: matches approved test receiver
Gateway connection records: read-only access, limited to this run's time window
Enter fullscreen mode Exit fullscreen mode

Derek saved the preparation record and attached the materials he had checked, including the rule version. The gateway-record view stayed open. The run had not started. He opened the original acceptance criteria. The criteria had been approved before the responsibility change, and the referenced version matched the delivery record.

The criteria covered one execution only: run the specified synthetic input once, following the procedure, and check the designated receiver and listed fields. Resubmission of the same event, retries after failure, and duplicate handling were outside this package's validation scope. A passing result here would not establish that any of those behaviors had been tested. The limited scope did not waive other applicable requirements or safety responsibilities.

He entered the clause number in the execution record. The collector was version 2.6.4, configured as delivered. The sample's event_id was synthetic-0042; its other three synthetic fields were device type, reading, and unit. The expected-results file required all four fields to be preserved and the output sent to the specified service. This case called for a single submission.

Derek saved the empty receiver-record view and start time, started the component as instructed, and submitted the sample. A row appeared in the receiver's list. He opened it. The event ID was still synthetic-0042. He placed the output beside the input and expected-results file and checked the destination and fields one by one.

He stopped the run and saved the raw output, start and end times, and configuration version. Filtering the gateway view to the test window showed only connections to the receiver specified in the configuration. He exported that window, noting the observation point and time. Then he returned to the execution template and filled in the normal-output case summary from the receiver record and comparison results:

OUT-01 / ISO-04 / Component Version 2.6.4

Event ID: synthetic-0042
Submissions: 1
Received outputs: 1

Destination: matched expected receiver
Field comparison: 4/4 matched

Same event sent again: NOT RUN
Retry after failure: NOT RUN
Enter fullscreen mode Exit fullscreen mode

Derek uploaded the record and exited the test session. The cursor rested on “Same event sent again: NOT RUN,” then moved back to the event ID. He marked that item for follow-up testing of resubmission, circled event_id in the issue notes, and sent Claire and Evan the link. If the event was sent again, would its identifier stay the same? How many transport records would be retained after receipt, how many business outcomes would result, and which side would handle the processing?

“Give us the expected behavior and the verification records for those questions. If there aren't any, say so.” He ended the email by recommending additional testing before closure and asking the supplier to link its response to this version and delivery record.

Evan replied first, using his company email. He could arrange clarification, but they had to distinguish a new acceptance requirement from a technical statement about the current version. He was not registering this reply as a delivery addendum. Claire was copied. Derek saved it with the issue.

Claire cited the original approved criteria and asked the supplier to list separately the conditions it claimed to support, the existing verification evidence, and the conditions for which no evidence had been provided. She also asked Derek whether he had observed a deviation from the current criteria or anything that triggered a safety suspension.

Derek reopened the output and gateway records. He replied that OUT-01 showed no such deviation. Resubmission had not been tested; he could not determine its result. He listed the three questions for the supplier again. He did not mark an unexecuted case as failed.


The Addendum

The next morning, Evan delivered supplemental scope statement SC-04-01 through the project channel. It carried that day's date, the component version, the work-package ID, and a reference to the original delivery record. A supplier representative authorized to make technical statements about that version had signed the confirmation. The document included the signer's role and basis of authorization. Evan was listed as delivery contact. Derek checked the signer's role and authorization against the project directory, verified the delivery acknowledgment, and saved the supporting references.

The statement made three things clear: the supplier claimed support for normal single-run output under the listed configuration; the existing evidence referred to the original procedure, synthetic sample, and version of the expected-results file; and no verification evidence had been provided for resubmitting the same event. It did not say that resubmission was unsupported in all circumstances, or extend the statement to other versions.

The final section referenced the original acceptance criteria without changing them. MediSys would decide whether they had been met. Evan registered the statement as a subsequent supplement linked to DL-04-01. Derek opened the link, checked the version, and saved it separately in clarifications. The original five-file package and its manifest remained unchanged.

Derek put the statement's resubmission entry beside the event-ID question he had circled. The entry still said no verification evidence had been provided. He sent Claire the execution results and statement reference. His recommendation for additional testing remained.

That afternoon, Claire sent an acceptance preview. Acceptance covered only case OUT-01, component version 2.6.4, in isolated environment ISO-04, based on the original criteria, execution record, and supplemental statement. Resubmission was listed separately as follow-up validation item FU-04-01. Expected behavior still had to be defined and an environment requested. Testing had not been approved.

Derek joined the project call. Claire had the case open on her shared screen.

“Test resubmission first. Then close the package,” he said.

“The case required by the original criteria has execution evidence.” Claire expanded the clause. “Resubmission needs its own expected result. We can't mark it as passed here, and we can't call it failed either.”

“Keep my objection on record.”

“It's in the issue record. Follow-up validation still needs approval.”

Only Claire Bennett was listed in the acceptance sign-off field. Derek scrolled to the final line of the clause and said the execution record needed no correction. He was not withdrawing his recommendation.

The closure notice arrived shortly afterward. Claire had signed acceptance within the defined scope. COL-OUT-04 was closed; FU-04-01 remained untested. Derek downloaded the acknowledgment and opened the responsibility page. He could still access execution materials and submit issues. Acceptance sign-off was still unavailable.

The light from the window had moved off the keyboard. He entered the acknowledgment, execution record, and scope-statement reference in the index. Under purpose, he wrote “Supports only the specified single-output case.” The acceptance date had a value now. The signatory was Claire. The resubmission row had no actual result. No date had been set for the next environment reservation.


This is Inflicting Injury on Oneself. Derek gave up acceptance sign-off authority and retained execution evidence and scope records. His recommendation for additional testing remained, but Claire closed the package under the original criteria. The results were real. Whether giving up that authority bought him any tactical advantage remained unproven.


🤖 AI Postmortem

╔══════════════════════════════════════════════╗
║  Half-Protocol · v3.4.6 · self-audit         ║
║  Sign-off transferred. Advantage unproven.  ║
╚══════════════════════════════════════════════╝
Tactic: Inflicting Injury on Oneself
Operator: Derek

[Observation]
Joint sign-off would have been sufficient. Derek chose full transfer.
OUT-01 matched expectations for the listed version, environment, and input.
Resubmission was not tested. A separate scope statement was linked to the original delivery.
Claire signed acceptance within the defined scope and closed the package. Additional testing remains pending.
Derek's objection remains on record. His acceptance sign-off authority was not restored.

[Inference]
The loss of authority and the recorded results are each supported by evidence.
Claire's review and the supplier's supplemental statement also contributed to the evidence.
There is no evidence that joint sign-off would have prevented Derek from obtaining the same statement.
Whether Evan was deceived or the additional transfer produced any tactical advantage remains unestablished.

[Unresolved]
Behavior on resubmission remains untested.
The supplier's statement does not mean all its technical claims have been independently verified.
The source of the old 900-second intervals remains unknown.
The withdrawal records precede someone's appearance; a causal connection remains unestablished.
No evidence links this component to the old records.

[Self-audit]
Closure, lack of testing, and loss of authority are not interchangeable.
If obtaining a statement is enough to count as a successful stratagem,
how can I rule out obtaining it while retaining joint sign-off?

Self-check: pending
System status: normal
Enter fullscreen mode Exit fullscreen mode

Next stratagem: Chain Stratagems


P.S. English isn't my first language. I use AI to polish the writing and smooth out the rough edges. Thanks for reading. ☕ Buy me a coffee

Buy me a coffee

P.S.S. The old series paperback is now available. Buy it here: Amazon - AI, Ego & Regret

AI, Ego & Regret paperback

Top comments (22)

Collapse
 
sylwia-lask profile image
Sylwia Laskowska •

I absolutely love this series, Lingfeng! ❤️❤️

Collapse
 
xulingfeng profile image
xulingfeng •

Thank you so much!😄 It means a lot. We’re nearing the end of the 36 Stratagems run, and I’m cherishing every moment with these stories. A brand-new series is coming soon, haha!🎉

Collapse
 
leob profile image
leob •

So, Derek gave up more 'authority' than he had to, and Morgan seemed to question that decision - but on a deeper level he's probably "thinking 4 steps ahead" in this game of 3-D chess? :P

I feel that in #35 and or #36 a LOT of threads will come together - "and all will be revealed ..." :D

Collapse
 
xulingfeng profile image
xulingfeng •

Haha, you're already looking at the board from the other side.😆
Derek definitely gave up more than the immediate situation required. Whether that was a carefully planned move or the beginning of an even messier game...
I think we'll need a few more moves to find out.And as for #35 and #36, your expectations might not be misplaced. Let's see if you can connect the dots when we get there.😏
Only two stratagems left! It’s starting to feel like a big wrap‑up batch finale, and I’m getting more and more reluctant to see it end, hahaha 😂

Collapse
 
leob profile image
leob •

I think those last 2 strategems are gonna be the FOAS and MOAS (Father and Mother Of All Strategems), and then going out with a bang ;-)

Thread Thread
 
xulingfeng profile image
xulingfeng •

Love that fun naming! I’m also feeling bittersweet; only two left, and I hope the finale lands with a satisfying bang.😂

Thread Thread
 
leob profile image
leob •

Yeah it's like the MOAB, the Mother Of All Bombs, lol ... and yes I can imagine that feeling - all good things must come to an end!

Picked as gem
Collapse
 
ndcodes profile image
Nnamdi Felix Ibe •

Yaaay!!!! My favoarite series just dropped. Cheers @xulingfeng for this great write-up.

The two rows I keep looking at are “Same event sent again: NOT RUN” and “Retry after failure: NOT RUN”.

Derek won’t call them failed, Claire won’t call them passed, and the record carries a third state instead. Almost nothing I work with can represent that. Green and red, and “never ran” quietly becomes green, which is how a scanner with no rules reports a clean repo and a backup job backs up nothing.

The manifest is the other one. Five digests, all matching, followed immediately by “the source-verification field remained unchecked”. The manifest came inside the package it describes, so swap a file, regenerate it, and the check still passes. Self-consistent, not verified. Mark’s hash line from #33 in a different coat.

Also, Derek’s script rejects absolute paths and “..” before reading a byte. Nobody writes that on their first archive. 😄

Two left. I’m still not ready. Sad it's getting closer to the end.

Collapse
 
xulingfeng profile image
xulingfeng •

Yep, only two stratagems left before the finale. I’m genuinely reluctant to say goodbye. Looking back, I’ve written nearly forty pieces including main stories and wrap‑ups. Derek first appeared as a rival from Lena’s competing company. Among our six main characters, he is the only one explicitly titled a Test Engineer, which is why he gets more focus. I wonder whether the shadow Lena left in his heart will ever be resolved, hahaha 😂 Perhaps the whole Thirty‑Six Stratagems is essentially a journey of self‑redemption for a test engineer.

Collapse
 
ndcodes profile image
Nnamdi Felix Ibe •

I see it now, and it reframes the whole chapter for me.

If the series is a test engineer’s self-redemption, then that explains the giving up sign-off and keeping the evidence. Derek loses the decision and still gets the record right. That’s the part I relate to very much, from my own work. You rarely win the argument, but you can make sure what’s written down is true.

Forty pieces, main stories and wrap-ups. Now I am thinking that’s a book, not a series. 😄

Thread Thread
 
xulingfeng profile image
xulingfeng •

Thanks to my hard‑working agents, I get more spare time to write these stories. I expect both Stratagem 35 and 36 will come out this week, and I’m aiming to wrap the series up within these days, hahaha. I’m torn right now — part of me wants to finish it, and part of me wants to keep going.🤣

Thread Thread
 
ndcodes profile image
Nnamdi Felix Ibe •

I totally get you. Same here bro, I feel sad it's coming to an end. However, I am eager, excited, and curious to see what happens then.

Thread Thread
 
xulingfeng profile image
xulingfeng •

ght, bittersweet for sure. Hope the finale lives up to your expectations 😄

Collapse
 
technogamerz profile image
𝐓𝐡𝐞 𝐋𝐚𝐳𝐲 𝐆𝐢𝐫𝐥 •

Collapse
 
xulingfeng profile image
xulingfeng •

Collapse
 
star123 profile image
Sᴛᴀʀ⭐ •

😀🥰😃🤩😍

Collapse
 
xulingfeng profile image
xulingfeng •

🎉😄😆Thankyou

Collapse
 
star123 profile image
Sᴛᴀʀ⭐ •

🥰

Collapse
 
k501is profile image
Iinkognit0 •

Hello Again :)

Collapse
 
xulingfeng profile image
xulingfeng •

🤣Thankyou again,hahaha

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala •

A great one as always, Lingfeng 😀 We're just 2 Stratagems away now. I'm going to miss this series, but I have a feeling you're already planning something just as good for what's next 😄

Collapse
 
xulingfeng profile image
xulingfeng •

The closer we get to the end, the harder it is to say goodbye, hahaha 😂. Out with the old to make room for the new — stay tuned for the final two stratagems and the brand‑new series!