TDD for my conceptional framework

I have the feeling that I can use skills from test-driven-development to build a conventional framework for organizing scientific papers. The name TDD is very bad, as I don't write tests, and the result is more related to architecture than programming as it regards the organization of files, not the creation of the content of them. Anyway, let's try it.

I start with a problem in mind without knowing how to solve it. I also lack knowledge of the required area. The plan is to build this knowledge trough papers. Let's start.

1. I start with an empty framework. It is the simplest one possible and can represent nothing.
2. I pop the first paper form the queue. How this queue is filled is another topic, but it represents all relevant papers.
3. I give the paper a category. Still, rather simple as it does not have to fit
4. I pop the next one
5. I connect it with an existing category or add it to the current category
6. I refactor, which means splitting, reorganizing, and so on so that the whole model fits.
7. I go to step 4

To relate with TDD, here are the three rules of TDD:

1. You are not allowed to write any production code unless it is to make a failing unit test pass.
2. You are not allowed to write any more of a unit test than is sufficient to fail, and compilation failures are failures.
3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.

Rewritten for my purpose:

1. You are not allowed to extend your conceptual model unless you have a paper that does not fit.
2. You are not allowed to pop more papers from the queue that is sufficient that you have to extend your model.
3. You are not allowed to extend your model than it is sufficient that you can add the current paper.

When you refactor, it is not allowed that one paper does not fit anymore in a category. 

The whole process is still very drafty as it is work in progress.